-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8324553: Shenandoah: Move periodic tasks closer to their collaborators #17540
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
8324553: Shenandoah: Move periodic tasks closer to their collaborators #17540
Conversation
👋 Welcome back wkemper! A progress list of the required criteria for merging this PR into |
@earthling-amzn The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
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.
I need to look at it with fresh eyes tomorrow, but a couple of stylistic comments now:
src/hotspot/share/gc/shenandoah/shenandoahMonitoringSupport.cpp
Outdated
Show resolved
Hide resolved
src/hotspot/share/gc/shenandoah/shenandoahMonitoringSupport.hpp
Outdated
Show resolved
Hide resolved
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 fine.
@earthling-amzn 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 23 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@shipilev) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@earthling-amzn |
/sponsor |
Going to push as commit 32eb529.
Your commit was automatically rebased without conflicts. |
@shipilev @earthling-amzn Pushed as commit 32eb529. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This is a refactoring to move Shenandoah's periodic tasks from the control thread to their respective dependencies: the pacer and monitoring support. This change will facilitate reviews of the upcoming changes to isolate the generational mode changes.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17540/head:pull/17540
$ git checkout pull/17540
Update a local copy of the PR:
$ git checkout pull/17540
$ git pull https://git.openjdk.org/jdk.git pull/17540/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17540
View PR using the GUI difftool:
$ git pr show -t 17540
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17540.diff
Webrev
Link to Webrev Comment