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
8267894: Skip work for empty regions in G1 Full GC #5143
8267894: Skip work for empty regions in G1 Full GC #5143
Conversation
|
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 think the change looks good in general, but maybe we should go with a "named" state for free regions. Either we change the name for the default value in G1FullGCHeapRegionAttr
or we add a new state that we set for free regions. What do you think?
AFAIK, changing the default value to "Free" instead of "Invalid" would suffice, however, need to clarify on how that is handled by |
I think the text "not initialized yet" is a bit wrong. We should never call is_skip_marking() for objects in "Invalid" regions, because there can't be any objects there. Same goes for "Free" regions. So I would change the assert to something like:
I agree that changing the default value should work. One benefit of using a new state could be to have a difference between free and not committed regions. But not sure it is worth the effort right now. |
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 to me.
@walulyai This change now passes all automated pre-integration checks. 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 72 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.
|
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.
Lgtm.
Going to push as commit d542745.
Your commit was automatically rebased without conflicts. |
Hi all,
Please review this change to skip doing work on regions that were empty at the beginning of the Full GC in phases that execute on a per-region basis.
Testing: Tier 1-3.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5143/head:pull/5143
$ git checkout pull/5143
Update a local copy of the PR:
$ git checkout pull/5143
$ git pull https://git.openjdk.java.net/jdk pull/5143/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5143
View PR using the GUI difftool:
$ git pr show -t 5143
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5143.diff