JDK-8131319 : Move G1Allocator::_summary_bytes_used back to G1CollectedHeap
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 9
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2015-07-15
- Updated: 2015-09-10
- Resolved: 2015-07-23
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.
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 |
|---|
9 b77Fixed  |
Related Reports
|
Relates :
|
Description
G1Allocator::_summary_bytes_used tracks the amount of memory used in regions that are not currently managed by G1Allocator or G1ArchiveAllocator. This member seems to be misplaced in G1Allocator because G1Allocator does not use it at all. G1CollectedHeap actually manages this value, there are multiple accessor functions just for it. G1CollectedHeap is the only one ever interested in total memory value, needing to sum up all components from all Allocators anyway. So I think the best option is to move _summary_bytes_used back to G1CollectedHeap, and let G1Allocator just be responsible for managing the memory it currently uses, until a better place is found.