RFR: Make weakref processing always use Executor

[Roman Kennke]

You think? I think it's cleaner this way.
If all GCs adopted this approach, it could simplify the code paths in RP a *lot*. It could be taken even further:
- move 1 threaded execution as VMThread into WorkGang to begin with (thus avoiding this special casing in each GC)
- fold upcoming MT-WeakProcessor into executor too, thus getting rid of the extra clutter to drive that.

Roman


Am 13. August 2018 11:12:13 MESZ schrieb Aleksey Shipilev <shade at redhat.com>:
>On 08/10/2018 06:47 PM, Roman Kennke wrote:
>> Incremental:
>> http://cr.openjdk.java.net/~rkennke/weakrefs-1thread/webrev.01.diff/
>> Full:
>> http://cr.openjdk.java.net/~rkennke/weakrefs-1thread/webrev.01/
>
>OK. It is still ugly-ish to always go to executor to avoid our own
>oom-evac-scope bugs, but oh well.
>
>-Aleksey

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