-
Notifications
You must be signed in to change notification settings - Fork 6.3k
8368954: G1: Document why G1 uses TLS storage for the current card table reference #27573
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
8368954: G1: Document why G1 uses TLS storage for the current card table reference #27573
Conversation
👋 Welcome back tschatzl! A progress list of the required criteria for merging this PR into |
@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 8 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 |
Webrevs
|
// E.g. embedding an address to that value directly into the code stream similar | ||
// to Serial/Parallel and then loading from that was found to be slower at least |
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.
Not sure if I misunderstood this text or not, but Serial/Parallel doesn't embed the "address" into the code stream -- they embed the actual value in the code stream, since the value (card-tabe-base) is constant. G1 can't/doesn't do that, since card-table-base is not constant.
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.
But G1 can embed the address of the value in the code stream, similar to Serial/Parallel (which embed the actual base address). The emphasis should be on the embedding, not what is embedded.
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.
maybe just remove the "an address" to avoid the confusion?
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.
It's my misunderstanding then. How about just dropping "similar to Serial/Parallel"? I don't see any benefit of referencing them here.
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.
maybe just remove the "an address" to avoid the confusion?
I think you need the "address" to connect with the latter "loading from that" -- "that" refers to the "address", doesn't it?
Thanks @robcasloz @walulyai @albertnetymk for your reviews |
Going to push as commit 1188ca5.
Your commit was automatically rebased without conflicts. |
Hi all,
please review some documentation update why G1 now uses TLS storage to get the current card table base value for the card mark.
TLDR: it's the overall fastest currently available way.
Testing: local compilation, this is just a trivial documentation change.
Thanks,
Thomas
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27573/head:pull/27573
$ git checkout pull/27573
Update a local copy of the PR:
$ git checkout pull/27573
$ git pull https://git.openjdk.org/jdk.git pull/27573/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 27573
View PR using the GUI difftool:
$ git pr show -t 27573
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27573.diff
Using Webrev
Link to Webrev Comment