JDK-8156754 : Encapsulate task queue policies into queue/task specific classes to use
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 9
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2016-05-11
  • Updated: 2022-02-02
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8280705 - Parallel: Full gc mark stack draining should prefer to make work available to other threads
Relates :  
JDK-8280396 - G1: Full gc mark stack draining should prefer to make work available to other threads
Relates :  
JDK-8152438 - Threads may do significant work out of the non-shared overflow buffer
Relates :  
JDK-8280958 - G1/Parallel: Unify marking code structure
Description
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).