RFR: 8364212: Shenandoah: Rework archived objects loading [v5]

Kelvin Nilsen kdnilsen at openjdk.org
Sun Aug 3 22:42:55 UTC 2025


On Sun, 3 Aug 2025 22:36:51 GMT, Kelvin Nilsen <kdnilsen at openjdk.org> wrote:

>> I believe yes, we only report the _humongous_ waste in ShenandoahAllocRequest. The rest of the waste is accrued right in `retire_from_partition`: https://github.com/openjdk/jdk/blob/8e921aee5abb20c240b45cb75b06fb1f316d8a1f/src/hotspot/share/gc/shenandoah/shenandoahFreeSet.cpp#L373-L376
>
> The "theory" is that if the remainder of this region is available for allocations, then we should not count the remnant as humongous_waste.  Is there any reason why we could not allow additional allocations within the CDS regions?

I agree that if we need to prevent further allocations in this region, then calling retire_from_partition() will account for the remnant memory as used and will prevent further allocations from this region.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/26510#discussion_r2250161916


More information about the hotspot-gc-dev mailing list