JDK-8150134 : Simplify concurrent refinement thread deactivation
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 9
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2016-02-18
- Updated: 2018-05-24
- Resolved: 2016-02-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.
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 b109Fixed  |
Related Reports
|
Relates :
|
Description
Concurrent refinement threads explicitly compare the current number of buffers with their deactivation threadhold to determine whether to deactivate. They also call apply_closure_to_completed_buffer with a "stop_at" of the green zone value, and deactivate if it returns false. It would be simpler to skip the explicit check for deactivation and just call apply_closure_to_completed_buffer with the deactivation threshold as the stop_at value.