-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8320318: ObjectMonitor Responsible thread #19454
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
8320318: ObjectMonitor Responsible thread #19454
Conversation
|
👋 Welcome back fbredberg! A progress list of the required criteria for merging this PR into |
|
@fbredber 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 84 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 |
|
@fbredber this pull request can not be integrated into git checkout 8320318_objectmon_responsible_thread
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 |
Webrevs
|
|
I've done basic testing on ppc64le, riscv64 and s390x using QEMU, but would appreciate if @TheRealMDoerr, @RealFYang and @offamitkumar could take it for a real test drive. |
|
Works with The JBS issue refers to "memory barriers (not a fence)", but you're using |
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 is such a nice simplifying change. I have some more suggestions.
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.
I've started looking at this and to be honest I'm surprised by the extent and complexity of the changes. The problem description sounded quite simple: get rid of the notion of the Responsible thread by putting in the fence that when missing could lead to stranding. I find it very hard to map many of the actual code changes to that problem statement. And I'm very unclear about the impact on the deflation protocol that this is causing.
I think trying to look at diffs is the wrong way to analyze this change, I need to just look at the new code and try to understand the protocol - but that makes it hard to put comments into the PR. :(
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.
Performed hs-tier1 - hs-tier3 tests on linux-riscv64 platform. Two minor comments for the riscv part.
|
@fbredber, @dholmes-ora: I got a substantial performance drop on our 96 Thread Xeon server: |
What OS for the Xeon? We have only seen issues with Windows. |
Sorry, I forgot to mention that it's linux (SUSE Linux Enterprise Server 15 SP4). |
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 looks great. Very nice work!
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.
I've taken another pass through and have a few queries.
Thanks
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 looks generally good to me. Found some weirdness, but I think we can fix it after this goes in. Some nit too but I don't need to see the updated patch for that. Thanks for fixing this!
|
@TheRealMDoerr @offamitkumar |
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 is really good. I have an issue with a new comment which might conflict with another reviewer.
Thanks for rebasing! The PPC64 implementation still looks good and some quick tests have passed on real hardware. I'll run more tests. |
s390x Changes looks good and I ran test and didn't see any regression. |
|
Test results on PPC64 look good. Is it already documented somewhere that |
Thank you for testing on PPC64. I've added the missing documentation here. |
|
Thanks all for good review comments and testing. |
|
/integrate |
|
Going to push as commit 180affc.
Your commit was automatically rebased without conflicts. |
Removed the concept of an ObjectMonitor Responsible thread.
The reason to have an ObjectMonitor Responsible thread was to avoid threads getting stranded due to a hole in the successor protocol. This hole was there because adding the necessary memory barrier was considered too expensive some 20 years ago.
The ObjectMonitor Responsible thread code adds complexity, and doing timed parks just to avoid getting stranded is not the way forward. More info about the problems with the ObjectMonitor responsible thread can be found in JDK-8320318.
After removing the ObjectMonitor Responsible thread we see increased performance on all supported platforms except Windows. JDK-8339730 has been created to handle this.
Passes tier1-tier7 on supported platforms.
x64, AArch64, Riscv64, ppc64le and s390x passes ok on the test/micro/org/openjdk/bench/vm/lang/LockUnlock.java test.
Arm32 and Zero doesn't need any changes as far as I can tell.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/19454/head:pull/19454$ git checkout pull/19454Update a local copy of the PR:
$ git checkout pull/19454$ git pull https://git.openjdk.org/jdk.git pull/19454/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 19454View PR using the GUI difftool:
$ git pr show -t 19454Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/19454.diff
Webrev
Link to Webrev Comment