-
Notifications
You must be signed in to change notification settings - Fork 231
8340547: Starting many threads can delay safepoints #3263
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
base: master
Are you sure you want to change the base?
Conversation
👋 Welcome back snazarki! A progress list of the required criteria for merging this PR into |
❗ This change is not yet ready to be integrated. |
This backport pull request has now been updated with issue from the original commit. |
@snazarkin This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
@snazarkin This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the |
@snazarkin Can you reopen this pull request ? |
/open |
@snazarkin This pull request is now open |
/reviewer credit @olivergillespie |
@snazarkin |
@snazarkin |
/reviewers 1 |
@snazarkin |
@olivergillespie could you please review the patch? |
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.
The implementation looks fine, but I don't know enough about any changes between 17 and 21/tip to be totally confident - we left vm_block as default false in tip, too, so that seems right, but 17 does seem to set vm_block=true a lot more than tip, I don't know why, maybe JDK-817639.
I'd like to backport this fix to fix the issue with starting a lot of threads in a burst.
Despite the low priority of this issue, some users have found this to be a barrier to migrating from JDK8.
The backport is not clean as it needs to adjust
globals.hpp
and replaceConditionalMutexLocker
with classic MutexLocker. The ranknonleaf
ofUseThreadsLockThrottleLock
has been chosen to be as close as possible to the rank ofThreads_lock
and to not cause a crash in debug mode:Field
_allow_vm_block
is set tofalse
to preventSimilar PR is on review at jdk21
Original fix and discussion are openjdk/jdk#21111
Tested with tier1 (release), tier2(fastdebug), and reproducers from JDK-8340547, JDK-8307970
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/3263/head:pull/3263
$ git checkout pull/3263
Update a local copy of the PR:
$ git checkout pull/3263
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/3263/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 3263
View PR using the GUI difftool:
$ git pr show -t 3263
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/3263.diff
Using Webrev
Link to Webrev Comment