RFR: Degenerated GC mode for Traversal

[Aleksey Shipilev]

On 03/27/2018 03:30 PM, Roman Kennke wrote:
>>> OTOH, this is a matter of luck. If it runs OOM after the check, it will
>>> go to full-gc anyway?
>>
>> Yes. So I am thinking that we can just slide to cleanup after final-traversal failure, and then the
>> allocation failure handling would restart degen-traversal itself from the known "clean" state? The
>> only difference against diving into STW straight away would be non-allocating mutators running while
>> alloc-failure is pending. Which seems to be no different from any other alloc-failure pending. No
>> need for separate degen point as well.
>>
> 
> Right, this seems the easiest solution.
> 
> Diff:
> http://cr.openjdk.java.net/~rkennke/traversal-degen/webrev.04.diff/
> Full:
> http://cr.openjdk.java.net/~rkennke/traversal-degen/webrev.04/
> 
> Ok now?

Yes, good to go.

Add a new-line in-between here:

1671       return;
1672     case _degenerated_outside_cycle:

Thanks,
-Aleksey