8253411: [BACKOUT] [REDO] G1 incorrectly limiting young gen size when using the reserve can result in repeated full gcs

[tschatzl]

Hi all,

can I have some reviews for this change that reverts commit fa30241.

Fix some merge error in this hunk:

From 3570f5a9, 8252041: G1: Fix incorrect uses of HeapRegionManager::max_length , the method "max_expandable_regions()" has been changed to "max_regions()" so the first use of it in the hunk

@@ -108,11 +107,14 @@ void G1Policy::init(G1CollectedHeap* g1h, G1CollectionSet* collection_set) {

• if (!use_adaptive_young_list_length()) {
• _young_list_fixed_length = _young_gen_sizer->min_desired_young_length();
• }
  _young_gen_sizer->adjust_max_new_size(_g1h->max_regions()); // <------------- here!

Did not revert cleanly. Everything else is unchanged.

Testing: local compilation. tier1-tier3 running

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JDK-8253411: [BACKOUT] [REDO] G1 incorrectly limiting young gen size when using the reserve can result in repeated full gcs

Reviewers

• Kim Barrett (@kimbarrett - Reviewer)
• Stefan Johansson (@kstefanj - Reviewer)

Download

$ git fetch https://git.openjdk.java.net/jdk pull/281/head:pull/281
$ git checkout pull/281

[bridgekeeper]

👋 Welcome back tschatzl! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@tschatzl The following label will be automatically applied to this pull request: hotspot-gc.

When this pull request is ready to be reviewed, an RFR email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label (add|remove) "label" command.

[mlbridge]

Webrevs

• 00: Full (c427ea7)

[kimbarrett]

Looks like a good backout. Disappointing...

[openjdk]

@tschatzl This change now passes all automated pre-integration checks. In addition to the automated checks, the change must also fulfill all project specific requirements

After integration, the commit message will be:

8253411: [BACKOUT] [REDO] G1 incorrectly limiting young gen size when using the reserve can result in repeated full gcs

Reviewed-by: kbarrett, sjohanss

• If you would like to add a summary, use the /summary command.
• To credit additional contributors, use the /contributor command.
• To add additional solved issues, use the /issue command.

Since the source branch of this PR was last updated there has been 1 commit pushed to the master branch:

• 955c2e6: 8253303: G1: Move static initialization of G1FromCardCache to a proper location

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid automatic rebasing, please merge master into your branch, and then specify the current head hash when integrating, like this: /integrate 955c2e629279c9c625764895e65f3623bce9c19e.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[mlbridge]

Mailing list message from Thomas Schatzl on hotspot-gc-dev:

Hi,

On 21.09.20 12:03, Kim Barrett wrote:

thanks for your and Stefan's reviews. I will integrate as soon as
testing comes back clean if nobody objects.

Thanks,
Thomas

[kstefanj]

Looks good.

[tschatzl]

/integrate

[openjdk]

@tschatzl Since your change was applied there has been 1 commit pushed to the master branch:

• 955c2e6: 8253303: G1: Move static initialization of G1FromCardCache to a proper location

Your commit was automatically rebased without conflicts.

Pushed as commit bba948f.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.