RFR: Don't enter SATB pre-barrier when in traversal.
Roman Kennke
rkennke at redhat.com
Fri Jan 26 11:53:33 UTC 2018
Am 26. Januar 2018 12:17:51 MEZ schrieb Aleksey Shipilev <shade at redhat.com>:
>On 01/26/2018 11:43 AM, Roman Kennke wrote:
>> This is the fix for the problem that Zhengyu found. It's another side
>effect of turning on MARKING
>> during traversal. We need to ensure to not enter the SATB pre-barrier
>during traversal.
>>
>>
>http://cr.openjdk.java.net/~rkennke/traversal-no-pre-barrier/webrev.00/
>
>Okay.
>
>So maybe it is wrong to turn off MARKING during Traversal GC? Let GC
>state MARKING only mean regular
>concurrent marking cycle?
Yes I think so. Major GC phases (concmark, evac, uprefs, partial and traversal) should not overlap, and barrier code should positively select what it wants, and not exclude what it doesn't want.
Let me rewrite this stuff.
Roman
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
More information about the shenandoah-dev
mailing list