-
Enhancement
-
Resolution: Fixed
-
P4
-
None
-
b14
After JDK-8219613, there is only one remaining use of a shared dirty card queue. All other uses of dirty card queues are thread-local in one way or another (in the G1ThreadLocalData, or in some local object such as a G1ParScanThreadState or a thread-local closure object).
That remaining use (in G1RemSet::refine_card_concurrently) still needs a shared queue.
However, having one class which supports both the normal thread-local usage and that one shared usage makes the code more complicated and less performant than need be. The shared case should be separated out into its own class.
That remaining use (in G1RemSet::refine_card_concurrently) still needs a shared queue.
However, having one class which supports both the normal thread-local usage and that one shared usage makes the code more complicated and less performant than need be. The shared case should be separated out into its own class.
- relates to
-
JDK-8221363 Build failure after JDK-8220240 (Refactor shared dirty card queue)
- Resolved
-
JDK-8221360 Eliminate Shared_DirtyCardQ_lock
- Resolved
-
JDK-8209974 Eliminate shared PtrQueues
- Closed
-
JDK-8219613 Use NonJavaThread PtrQueues
- Resolved