RFR: Factor out storeval barrier from read barriers

[Roman Kennke]

OK. But it is not independent in this patch: turning off RB would also turn off the SVB. (Or, with upcoming partial GC, same with WBs). Would it be more useful to have them more independent?

Roman

Am 27. August 2017 09:20:58 MESZ schrieb Aleksey Shipilev <shade at redhat.com>:
>On 08/25/2017 08:37 PM, Roman Kennke wrote:
>> I also added a flag ShenandoahStoreValBarriers that does the same as
>the
>> other ShenandoahXXXBarriers flag, turn generation of the barriers off
>on
>> request. The way it's currently done, the storeval barrier is also
>> controlled by ShenandoahReadBarriers, dunno if we want to change
>that?
>> I.e. -ShReadBarrier not affect ShStoreValBarrier ?
>
>Making a separate ShStoreValBarrier is good with me. Having it separate
>from ShReadBarrier is good
>with me too, because I wondered what the impact on storeval barriers
>was.
>
>> http://cr.openjdk.java.net/~rkennke/storevalbarrier/webrev.00/
>
>This looks good.
>
>Thanks,
>-Aleksey

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.