-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8283566: G1: Improve G1BarrierSet::enqueue performance #7921
Conversation
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
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.
Maybe rename enqueue_oop
to enqueue_not_null
? This is a fairly common naming scheme for methods specialized that way.
Lgtm.
@shipilev 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 3 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
Thing is, it is not about nullity. It is about whether we have already loaded the oop or not. Maybe |
Okay. |
After some back and forth, I settled on |
Any opinions about this version? |
Thanks for reviews! /integrate |
Going to push as commit 6ebf845.
Your commit was automatically rebased without conflicts. |
While looking at startup/warmup benchmarks for VarHandles, I noticed that
G1BarrierSet::enqueue
is not inlined and quite hot. Its uses also load the oop first, and then check if queues are active. This could be improved a bit. This only matters for the barrier paths that VM takes, which is the case forjava.lang.invoke
VM infra.Not sure about
enqueue_oop
name, I did it to avoid accidental overload clash withenqueue(T* dst)
. Open for suggestions.On a simple test:
Baseline:
Patched:
Additional testing:
tier1
tier2
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/7921/head:pull/7921
$ git checkout pull/7921
Update a local copy of the PR:
$ git checkout pull/7921
$ git pull https://git.openjdk.java.net/jdk pull/7921/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 7921
View PR using the GUI difftool:
$ git pr show -t 7921
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/7921.diff