-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8270347: ZGC: Adopt release-acquire ordering for forwarding table access #4763
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
Conversation
Hi @weixlu, welcome to this OpenJDK project and thanks for contributing! We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user weixlu" as summary for the issue. If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing |
/covered |
/contributor add Hao Tang albert.th@alibaba-inc.com |
@weixlu |
Thank you! Please allow for a few business days to verify that your employer has signed the OCA. Also, please note that pull requests that are pending an OCA check will not usually be evaluated, so your patience is appreciated! |
#4597 implements memory_order_release for AArch64. We think this could benefit ZGC as well. |
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.
|
@weixlu 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 252 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 (@fisk, @pliden) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
Hi, it seems that a non-trivial patch requires at least two reviewers. @pliden would you please review this patch? |
I believe we're good because the release you've changed this to is matched by the ZForwarding::at() accesses the entries with an acquire, and I can find no other means of accessing entries. |
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.
@stooart-mon Thanks for reviewing. Could you please approve this pull request? |
I'm not a committer or reviewer, so I can't officially approve this. |
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!
I'll sponsor the change. |
@pliden @fisk @stooart-mon Thank you very much for your review. |
/integrate |
/sponsor |
Going to push as commit bdb50ca.
Your commit was automatically rebased without conflicts. |
ZGC forwarding table records entries to track the destination of object relocation. Currently, the entry insertion (ZForwarding::insert()) adopts memory_order_conservative to guarantee that (1) the object copy always happens before the installation of forwardee, and (2) the other thread that accesses the same entry (ZForwarding::at() with load_acquire semantic) is able to access the correct contents of the forwarded object.
Let us consider memory_order_release for the entry insertion in ZForwarding::insert(). Pairing with the entry access in ZForwarding::at(), the forwarding table adopts release-acquire memory ordering. The two statements we mentioned above can also be guaranteed by the release-acquire ordering.
We performed an experiment on benchmark SPECjvm2008.sunflow on AArch64. The concurrent relocation time is listed below. The optimized version results in shorter average concurrent relocation time. Furthermore, it could benefit the throughput of ZGC.
Progress
Issue
Reviewers
Contributors
<albert.th@alibaba-inc.com>
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/4763/head:pull/4763
$ git checkout pull/4763
Update a local copy of the PR:
$ git checkout pull/4763
$ git pull https://git.openjdk.java.net/jdk pull/4763/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 4763
View PR using the GUI difftool:
$ git pr show -t 4763
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/4763.diff