-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
8331714: Make OopMapCache installation lock-free #19100
8331714: Make OopMapCache installation lock-free #19100
Conversation
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
@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 48 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 |
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. Very similar to what I made in PR #16074
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.
This seems completely reasonable.
Thanks! /integrate |
Going to push as commit a2584a8.
Your commit was automatically rebased without conflicts. |
Trying to solve JDK-8331572 runs into all sorts of lock ranking issues with
OopMapCacheAlloc_lock
. I think it would be a bit saner to rewrite the double-checked locking installation to atomic lock-free. OpenJDK code was using this lock since the initial load.There is a drawback that we might be trying to instantiate multiple
OopMapCache
instances from multiple threads. I think this is not a practical problem, as only a few threads would race here, and the allocation is relatively small (32*8 = 512 bytes). In imaginary worst^W nightmare case, with 100K threads racing we get a temporary native memory spike at +50M.Additional testing:
all
testsProgress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/19100/head:pull/19100
$ git checkout pull/19100
Update a local copy of the PR:
$ git checkout pull/19100
$ git pull https://git.openjdk.org/jdk.git pull/19100/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 19100
View PR using the GUI difftool:
$ git pr show -t 19100
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/19100.diff
Webrev
Link to Webrev Comment