JDK-8153503 : Move remset scan iteration claim to remset local data structure
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 9
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2016-04-05
- Updated: 2018-06-21
- Resolved: 2016-04-19
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 b120Fixed  |
Related Reports
|
Blocks :
|
|
|
Relates :
|
Description
Currently, scanning the remset is a procedure that accesses and stores data about it its current state many different places. This results in many unrelated tasks that need to be done and additional verification code at certain points in the code, which bloats the code even more. Capture all this information into a single G1RemSetScanState to be able to extend and change this mechanism in the future without touching a large part of the code base. Also, scanning the remembered sets of regions in the collection set current employs a two-pass algorithm for no particular reason. Fix this.
Comments
|