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
8269596: Snapshot soft ref policy before marking/copying #4624
Conversation
|
@albertnetymk The following label 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 list. 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.
Would it be useful to only call the soft ref policy setup via setup_policy()
when it is (potentially) set to true
? I.e. only during full gc, and call setup_policy(false)
afterwards, maybe with a scope object?
This would remove the unnecessary calls with false
as argument completely in the places where we never actually change it (e.g. for the G1 concurrent mark ref processor), and emphasize for the stw full gc collectors that they are the only ones eventually change it to "always clearing". Feel free to ignore this suggestion, but it seems unnecessary to have setup_policy(false);
calls in a lot of places. Maybe if combined with below suggestion this one is obsolete.
Also the sequence
reference_processor()->enable_discovery();
reference_processor()->setup_policy(<some value>);
should be merged into a single call as there are like five places now where both are called one after another.
In psParallelCompact.cpp
, the marked_for_unloading
local right after these calls could be removed too, it's unused.
Merged |
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.
@albertnetymk 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 76 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.
|
I accidentally removed a call to |
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 for the review. /integrate |
Going to push as commit f8bcbf0.
Your commit was automatically rebased without conflicts. |
@albertnetymk Pushed as commit f8bcbf0. |
Set up soft ref policy before marking/copying for Serial, Parallel and G1. With this change, all collectors do soft-ref policy setup in the beginning of a GC cycle.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/4624/head:pull/4624
$ git checkout pull/4624
Update a local copy of the PR:
$ git checkout pull/4624
$ git pull https://git.openjdk.java.net/jdk pull/4624/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 4624
View PR using the GUI difftool:
$ git pr show -t 4624
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/4624.diff