-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8294845: Make globals accessed by G1 young gen revising atomic #10845
Conversation
👋 Welcome back tschatzl! A progress list of the required criteria for merging this PR into |
Webrevs
|
@tschatzl This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 74 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
Thanks @kimbarrett @walulyai for your reviews |
Going to push as commit 6626a29.
Your commit was automatically rebased without conflicts. |
Hi all,
can I have reviews for this cleanup that makes a few globals accessed by
G1Policy::update_young_length_bounds
"atomic" as per style guide? Basically there are a few variables that are changed by young gen size revising that are read concurrently, and to indicate that, this change decorates them with theAtomic
accessor functions.This is no attempt to fix any visibility races that (already, pre-existing) occur when these values are written and read; I think all of these are benign and can at most lead to having garbage collections that are "too late" or "too early" due to that. However all the young gen length revising, particularly in presence of the gclocker, is and has always been a best effort approach as far as I could ever tell.
Testing: gha
Thanks,
Thomas
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10845/head:pull/10845
$ git checkout pull/10845
Update a local copy of the PR:
$ git checkout pull/10845
$ git pull https://git.openjdk.org/jdk pull/10845/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10845
View PR using the GUI difftool:
$ git pr show -t 10845
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10845.diff