Integrated: 8252041: G1: Fix incorrect uses of HeapRegionManager::max_length

[Thomas Schatzl]

On Tue, 15 Sep 2020 13:10:28 GMT, Thomas Schatzl <tschatzl at openjdk.org> wrote:

> Hi all,
> 
>   can I have reviews for this change that fixes some uses of HeapRegionManager::max_regions()/max_expandable_regions() in
>   our code to use the correct variant?
> 
> HeapRegionManager::max_length gives the absolute maximum number of regions reserved for the heap based on the
> reservation.
> HeapRegionmanager::max_expandable_regions() returns the maximum number of regions the heap can grow to (can be
> committed).
> Typically they are exchangeable, but if the reservation is larger than what -Xmx allows (like when file-mapping old
> gen), this is not the case, and causes assertions. In some cases the existing region manager code could (if it reserved
> more than -Xmx) give back more than -Xmx allows.  Testing: tier1-5.

This pull request has now been integrated.

Changeset: 3570f5a9
Author:    Thomas Schatzl <tschatzl at openjdk.org>
URL:       https://git.openjdk.java.net/jdk/commit/3570f5a9
Stats:     121 lines in 15 files changed: 3 ins; 18 del; 100 mod

8252041: G1: Fix incorrect uses of HeapRegionManager::max_length

Reviewed-by: sjohanss, kbarrett

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

PR: https://git.openjdk.java.net/jdk/pull/178