RFR: JDK-8216973: Shenandoah: Kick up cleanup phases in the right places

Roman Kennke rkennke at redhat.com
Mon Jan 14 11:25:44 UTC 2019

In Shenandoah, we currently start cleanup phase when we dive into
concurrent evacuation (and only then), and after the cycle
(unconditionally). However, we only create trashed regions in final-mark
(immediate garbage and/or garbage from previous cycle), and might skip
evacuation altogether, and may not actually create trash at end of cycle
if we merge update-refs onto subsequent concurrent-mark. Let's start
cleanups where we actually need them: once unconditionally before
conc-evac and once after final-update-refs.


Testing: hotspot_gc_shenandoah

Also, should this go into JDK12?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://mail.openjdk.java.net/pipermail/hotspot-gc-dev/attachments/20190114/45b39401/signature.asc>

More information about the hotspot-gc-dev mailing list