Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8135680 | emb-9 | Thomas Schatzl | P5 | Resolved | Fixed | team |
There are a few issues with the allocation manager hierarchy in g1Allocator.?pp:
- G1ParGCAllocator should be renamed to G1PLABAllocator to conform to the "new" PLAB names (e.g. PLAB instead of ParGC)
- resolve some include cycles
- some additional documentation would be nice
- decrease the amount of back-and-forth between G1CollectedHeap and G1Allocator; hide G1AllocRegion from G1CollectedHeap
- G1ParGCAllocator should be renamed to G1PLABAllocator to conform to the "new" PLAB names (e.g. PLAB instead of ParGC)
- resolve some include cycles
- some additional documentation would be nice
- decrease the amount of back-and-forth between G1CollectedHeap and G1Allocator; hide G1AllocRegion from G1CollectedHeap
- backported by
-
JDK-8135680 Rename and clean up the allocation manager hierarchy in g1Allocator.?pp
-
- Resolved
-
- duplicates
-
JDK-8073317 Move all region level allocation related things into AllocRegionManager
-
- Closed
-
- is blocked by
-
JDK-8074546 Rename and clean up the ParGCAllocBuffer class
-
- Resolved
-
- relates to
-
JDK-8073317 Move all region level allocation related things into AllocRegionManager
-
- Closed
-
-
JDK-8030849 Investigate high fragmentation/waste in some situations during allocation during GC in G1
-
- Open
-