JEP 189: Shenandoah: An Ultra-Low-Pause-Time Garbage Collector
rkennke at redhat.com
Wed Feb 5 10:48:20 PST 2014
Am Mittwoch, den 05.02.2014, 13:00 -0500 schrieb Tony Printezis:
> On 2/4/14, 6:39 PM, Roman Kennke wrote:
> >> Will Shenandoah try to reuse the existing write barrier logic in
> >> HotSpot and extend it to catch all field writes as opposed to just
> >> reference field writes, or will it use some other form of write
> >> barrier?
> > It uses the G1 barrier for SATB and extends it for the preemptive
> > copying.
> But you didn't answer Krystal's question, though. :-) Given that the JEP
> says "All writes to objects in targeted regions must first copy the
> object and then write to the object in its new location", don't you have
> to extend the write barrier for scalar writes too?
Oh yes, exactly this is the case.
More information about the hotspot-gc-dev