RFR: Refactor allocation failure and explicit GC handling

Aleksey Shipilev shade at redhat.com
Wed Jan 17 09:03:50 UTC 2018


On 01/17/2018 10:01 AM, Roman Kennke wrote:
> Am 17.01.2018 um 09:32 schrieb Aleksey Shipilev:
> Infact, this is what happens with other GCs: allocation failure goes straight to
> VMThread::execute() ... I wonder if we could also do this and avoid the locking? But then, how to
> communicate with the ShConcThread ?

No, we should not do the VMOp right away. Our ShConcThread is really a Driver, and we need to tell
the Driver we have experienced allocation failure. Then it could decide what to do: Full GC,
Degenerated GC, continue with Conc GC, fail hard...

Thanks,
-Aleksey



More information about the shenandoah-dev mailing list