-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
8297495: j.u.concurrent updates for JDK 20 #11319
Conversation
👋 Welcome back alanb! A progress list of the required criteria for merging this PR into |
@AlanBateman The following label 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 list. If you would like to change these labels, use the /label pull request command. |
/csr |
@AlanBateman has indicated that a compatibility and specification (CSR) request is needed for this pull request. @AlanBateman please create a CSR request for issue JDK-8297495 with the correct fix version. This pull request cannot be integrated until the CSR request is approved. |
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.
I don't have enough knowledge of this area, but the API changes look OK to me.
With this addition of the externalSubmit
method should the javadoc of the existing submit
method be enhanced a bit to explain how it behaves differently as compared to this one and when to choose one over the other. For example, should submit
API state (its already existing behaviour) that it will use the current worker thread's queue to push this new task if called from the worker thread?
/** | ||
* Tests for ForkJoinPool and ForkJoinWorkerThread additions in JDK 20. | ||
*/ | ||
public class ForkJoinPool20Test extends JSR166TestCase { |
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 new externalSubmit
API states:
@implSpec
This method is equivalent to {@link #submit(ForkJoinTask)} when called
from a thread that is not in this pool.
Should this new test class include a test which verifies this behaviour? As far as I can see, the new test methods that assert the queue counts are being invoked from within a worker 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.
Thank you for the changes. This looks fine to me.
@AlanBateman 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 69 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 |
* scheduled for execution | ||
* @since 20 | ||
*/ | ||
public <T> ForkJoinTask<T> externalSubmit(ForkJoinTask<T> task) { |
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.
@AlanBateman Does it make sense to check the nullness of the task
before going into the storeStoreFence etc?
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's only to be the same as poolSubmit.
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.
@AlanBateman Then I presume that there's a good reason for not checking. :)
/integrate |
Going to push as commit 19d8498.
Your commit was automatically rebased without conflicts. |
@AlanBateman Pushed as commit 19d8498. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The proposed updates for JDK 20 are:
These methods will be used to improve the Thread.yield implementation for virtual threads. The range of alternatives explored include not exposing an API and protected methods such as "offerSubmission". The class description speaks of "external clients" and "submissions from non-ForkJoinTask clients", hence the proposed naming and javadoc text.
Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/11319/head:pull/11319
$ git checkout pull/11319
Update a local copy of the PR:
$ git checkout pull/11319
$ git pull https://git.openjdk.org/jdk pull/11319/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 11319
View PR using the GUI difftool:
$ git pr show -t 11319
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/11319.diff