8289822: G1: Make concurrent mark code owner of TAMSes#18150
8289822: G1: Make concurrent mark code owner of TAMSes#18150tschatzl wants to merge 10 commits intoopenjdk:masterfrom
Conversation
|
👋 Welcome back tschatzl! A progress list of the required criteria for merging this PR into |
…nge) to not potentially make HeapRegion::hr_clear() too slow
d27cc21 to
a5bbab8
Compare
|
@tschatzl Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
Webrevs
|
|
/label add hotspot-gc |
|
@albertnetymk |
|
@tschatzl this pull request can not be integrated into git checkout submit/8289822-concurrent-mark-tams-owner
git fetch https://git.openjdk.org/jdk.git master
git merge FETCH_HEAD
# resolve conflicts and follow the instructions given by git merge
git commit -m "Merge master"
git push |
|
@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 79 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 |
albertnetymk
left a comment
There was a problem hiding this comment.
Maybe add G1: in the title?
|
Thanks @albertnetymk @walulyai for your reviews |
|
Going to push as commit f1c69cc.
Your commit was automatically rebased without conflicts. |
Hi all,
please review this change that moves TAMS ownership and handling out of
HeapRegionintoG1ConcurrentMark.The rationale is that it's intrinsically a data structure only used by the marking, and only interesting during marking, so attaching it to the always present
HeapRegionisn't fitting.This also moves some code that is about marking decisions out of
HeapRegion.In this change the TAMSes are still maintained and kept up to date as long as the
HeapRegionexists (basically always) as the snapshotting of the marking does not really snapshot ("copy over theHeapRegions that existed at the time of the snapshot, only ever touching them), but assumes that they exist even for uncommitted (or free) regions due to the way it advances the globalfingerpointer.I did not want to change this here.
This is also why
HeapRegionstill tellsG1ConcurrentMarkto update the TAMS in two places (when clearing a region and when resetting during full gc).Another option I considered when implementing this is clearing all marking statistics (
G1ConcurrentMark::clear_statistics) at these places inHeapRegionbecause it decreases the amount of places where this needs to be done (maybe one or the other place isn't really necessary already). I rejected it because this would add some work that is dependent on the number of worker threads (particularly) intoHeapRegion::hr_clear(). This change can be looked at by viewing at all but the last commit.Testing: tier1-4, gha
Thanks,
Thomas
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/18150/head:pull/18150$ git checkout pull/18150Update a local copy of the PR:
$ git checkout pull/18150$ git pull https://git.openjdk.org/jdk.git pull/18150/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 18150View PR using the GUI difftool:
$ git pr show -t 18150Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/18150.diff
Webrev
Link to Webrev Comment