JDK-8201318 : Introduce GCThreadLocalData to abstract GC-specific data belonging to a thread
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 11
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-04-09
  • Updated: 2018-05-21
  • Resolved: 2018-04-12
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.
JDK 11
11 b10Fixed
Related Reports
Relates :  
JDK-8202705 - ARM32 build crashes on long JavaThread offsets
Description
As part of the effort to make GCs more pluggable, the G1-specific data in JavaThread should be moved out into a more appropriate abstraction.

This is the second step (building on JDK-8201316), which introduces GCThreadLocalData, an opaque data area in Thread. Each GC is free to decide the internal structure and contents of this area.

With this in place, we can remove G1's thread-local SATB queue and dirty card queue from JavaThread and instead let G1 use the data area provided by GCThreadLocalData to store these.