RFR: 8192647: GClocker induced GCs can starve threads requiring memory leading to OOME [v2]

[Albert Mingkun Yang]

On Tue, 18 Feb 2025 01:25:12 GMT, David Holmes <dholmes at openjdk.org> wrote:

> You still need it to be an atomic load

Then, maybe the logic is easier to read if the "atomic" access is visible directly from that context, instead of hiding it inside `in_critical`. Therefore, it probably makes more sense to introduce a new API. WDYT?

> The GCLocker behaviour would be easier to discern ...

Renamed to `current_thread` in `enter`,`exit`, and `enter_slow`.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/23367#issuecomment-2665044825