RFR: Locked allocation
Andrew Haley
aph at redhat.com
Thu Dec 15 12:01:56 UTC 2016
On 15/12/16 11:55, Aleksey Shipilev wrote:
> Think about this as coarsening the current juggling-the-knives
> lock-free mechanics with a spinlocked entry to the small critical
> section. We are not expected to do any heavy-lifting while holding
> that lock. This minimizes the need for sophisticated backoffs,
> etc. Pretty much how we don't usually think about backoffs with
> lock-free update code :)
OK.
Andrew.
More information about the shenandoah-dev
mailing list