JDK-8247878 : Move Management strong oops to OopStorage
- Type: Enhancement
- Component: hotspot
- Sub-Component: svc
- Affected Version: 16
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-06-18
- Updated: 2024-11-13
- Resolved: 2020-07-20
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 16 |
|---|
16 b07Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
ThreadService and MemoryService implementations collect information at a safepoint and after the safepoint create objects to pass back to Java code. The oops they collect are saved directly in the data structures necessitating an oops_do() call on them. If the oops are moved to OopStorage, they can be iterated more efficiently by GC. Also all the GCs won't require a case to call Management::oops_do().
Comments
|