RFR: 8370850: Shenandoah: Simplify collector allocation to save unnecessary region iteration [v3]
Xiaolong Peng
xpeng at openjdk.org
Thu Nov 6 17:27:34 UTC 2025
On Tue, 4 Nov 2025 23:08:11 GMT, William Kemper <wkemper at openjdk.org> wrote:
>> I have removed can_allocate_in_new_region again after merging @kdnilsen's change unifying accountings, since we don't have consistency in accountings anymore.
>
> We still need to enforce that requests for a young evacuation don't take memory that was reserved for old evacuations. `can_allocate_in_new_region` isn't about consistency between freeset and generation accounting, it's used to maintain old/young collector reserves.
I am confused again. My understanding is: we won't, that is is done by the partition, for young evacuation we will only look for regions in the Collector partition, if a region is FREE and reserved for old evacuations, the region will be in OldCollector partition.
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/28036#discussion_r2500016821
More information about the hotspot-gc-dev
mailing list