JDK-8073317 : Move all region level allocation related things into AllocRegionManager
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 9
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2015-02-17
  • Updated: 2015-08-05
  • Resolved: 2015-08-05
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 9
9Resolved
Related Reports
Duplicate :  
JDK-8073052 - Rename and clean up the allocation manager hierarchy in g1Allocator.?pp
Relates :  
JDK-8073052 - Rename and clean up the allocation manager hierarchy in g1Allocator.?pp
Relates :  
JDK-8030849 - Investigate high fragmentation/waste in some situations during allocation during GC in G1
Description
AllocRegionManager introduced in JDK-8073052 handles all allocation within regions. There is still a good amount of related methods in G1CollectedHeap that should be moved there.

This reduces the amount of dependencies between these two methods, and also cross-calls like AllocRegionManager->G1CollectedHeap->AllocRegionManager.
Comments
Merged with JDK-8073052 to avoid cleanup changes, then functional changes, and then cleanup changes (this change) again.
05-08-2015