JDK-7023151 : G1: refactor the code that operates on _cur_alloc_region to be re-used for allocs by the GC threads
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: hs21
- Priority: P4
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2011-02-28
- Updated: 2013-09-18
- Resolved: 2011-04-24
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 7 | Other |
|---|---|
7Fixed  |
hs21Fixed |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
Currently we have two versions of code that attempts to satisfy parallel allocation requests out of a heap region and attempts to replace said heap region when it's full: a) One version is for allocations by mutator threads. b) Another version is for allocations by GC threads (i.e., when they need to copy objects from from- to to-space). It'd be helpful to consolidate these two versions and have a single version of the code shared by the two paths above. This CR proposes the refactoring of the code of path a) in a separate class (G1AllocRegion). This is one step towards sharing this code by path b) (this will be done as a separate CR in the future).
Comments
|