JDK-8276304 : G1: Factor out G1CardSetFreePool and related classes from G1CardSetXxx
  • Type: Sub-task
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 18
  • Priority: P4
  • Status: In Progress
  • Resolution: Unresolved
  • Submitted: 2021-11-02
  • Updated: 2022-01-22
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
Blocks :  
JDK-8277542 - G1: Move G1CardSetFreePool and related classes to separate files
Blocks :  
JDK-8276670 - G1: Rename G1CardSetFreePool and related classes
Relates :  
JDK-8276670 - G1: Rename G1CardSetFreePool and related classes
Relates :  
JDK-8280106 - G1: Make reclaiming memory functionality more general in G1SegmentedArrayFreePool and G1SegmentedArrayFreeMemoryTask
Relates :  
JDK-8276094 - Region Pinning in G1
Description
Currently, only the card sets (remembered sets) use G1CardSetFreePool to give back memory to OS.

After JDK-8254739, this memory reclaiming mechanism could be reused by evacuation failure too. This is a preparation change to allow reuse of this code.

I plan to do this in about 3 steps to smooth the review process:
  1. move G1CardSetFreePool and related classes to new file, rename these classes
  2. refactor these classes to support freeing other freelist
  3. some necessary cleanup