While looking at JDK-8152438, we found that every user of the OverflowTaskQueue implements (and copies) some kind of strategy on how to manage the tasks within the various queues, implementing them somewhere into the code.
One very good refactoring would be to encapsulate these strategies, wrapping OverflowTaskQueue with a more simple interface (like push/pop/steal/is_empty only).
One very good refactoring would be to encapsulate these strategies, wrapping OverflowTaskQueue with a more simple interface (like push/pop/steal/is_empty only).
- relates to
-
JDK-8280705 Parallel: Full gc mark stack draining should prefer to make work available to other threads
-
- Resolved
-
-
JDK-8152438 Threads may do significant work out of the non-shared overflow buffer
-
- Resolved
-
-
JDK-8280396 G1: Full gc mark stack draining should prefer to make work available to other threads
-
- Resolved
-
-
JDK-8280958 G1/Parallel: Unify marking code structure
-
- Resolved
-