-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8255070: Shenandoah: Use single thread for concurrent CLD liveness test #777
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
👋 Welcome back zgu! A progress list of the required criteria for merging this PR into |
@zhengyu123 The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
@@ -1941,7 +1941,7 @@ class ShenandoahConcurrentWeakRootsEvacUpdateTask : public AbstractGangTask { | |||
ShenandoahVMWeakRoots<true /*concurrent*/> _vm_roots; | |||
|
|||
// Roots related to concurrent class unloading | |||
ShenandoahClassLoaderDataRoots<true /* concurrent */, false /* single thread*/> | |||
ShenandoahClassLoaderDataRoots<true /* concurrent */, true /* single thread*/> |
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.
Should the first input be false?
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.
No. It runs concurrently, so will need to acquire ClassLoaderGraph_lock.
assert(SafepointSynchronize::is_at_safepoint(), "Must be at a safepoint"); | ||
assert(Thread::current()->is_VM_thread(), "Can only be done by VM thread"); | ||
ClassLoaderDataGraph::always_strong_cld_do(clds); | ||
} | ||
} else if (_semaphore.try_acquire()) { |
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.
It looks to me that we do:
if (_semaphore.try_acquire()) {
in both branches now. Can this be reshaped to do try_acquire() and claim_all() outermost?
assert(SafepointSynchronize::is_at_safepoint(), "Must be at a safepoint"); | ||
assert(Thread::current()->is_VM_thread(), "Can only be done by VM thread"); | ||
ClassLoaderDataGraph::cld_do(clds); | ||
} | ||
} else if (_semaphore.try_acquire()) { |
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.
Same as above. Also, the only difference to above is cld_do() vs always_strong_cld_do(), with lots of identical boilerplate. Can this be refactored into a generic method that takes the final target method as argument?
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.
Refactored and retested. Thanks for the suggestion.
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.
Also, I'd change the commit message to begin uppercase after Shenandoah: "Use..."
if (SINGLE_THREADED) ClassLoaderDataGraph_lock->lock(); | ||
f(clds); | ||
if (SINGLE_THREADED) ClassLoaderDataGraph_lock->unlock(); | ||
_semaphore.claim_all(); |
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.
Would it be nicer to write this as follows?
if (SINGLE_THREADED) {
MutexLocker ml(ClassLoaderDataGraph_lock);
f(clds);
} else {
f(clds);
}
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! Thank you!
@zhengyu123 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 86 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 |
/integrate |
@zhengyu123 Since your change was applied there have been 87 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 615b759. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Since the concurrent liveness test does not touch any oops, there is no point to use multi-thread for the task, they just duplicate the work.
Also, multi-thread version requires to acquire ClassLoaderGraph_lock early, which is deadlock prone.
Progress
Testing
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/777/head:pull/777
$ git checkout pull/777