-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8318422: Allow poller threads be virtual threads #16243
Conversation
👋 Welcome back alanb! A progress list of the required criteria for merging this PR into |
@AlanBateman 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. |
/label remove net |
@AlanBateman |
Webrevs
|
* Returns true if this poller is for read (POLLIN) events. | ||
* Returns the poller's file descriptor, used when the read and write poller threads | ||
* are virtual threads. | ||
* |
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 useful to add some more explanation here like: "When there is no activity on any of a subpoller's descriptors, the descriptor of the subpoller is registered with the master poller" ?
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 useful to add some more explanation here like: "When there is no activity on any of a subpoller's descriptors, the descriptor of the subpoller is registered with the master poller" ?
The big comment on Mode.VTHREAD_POLLERS explains this. It also links to the Karsten/Barghi paper where a similar scheme is presented. Do you think that's enough?
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.
@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 3 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
Thanks. I've had to one additional update to ProblemList-Virtual.txt to excludevmTestbase/nsk/jdi/VMOutOfMemoryException/VMOutOfMemoryException001/VMOutOfMemoryException001.java on all platforms. It had been excluded on Windows only but it's quite fragile and we tickle it to fail on Linux with these changes. I had a brief exchange with @plummercj in JDK-8285417 about this a few days ago. It's excluded on all platforms in the loom repo already so I should have remembered to include it in this update. |
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.
Latest change is good.
/integrate |
Going to push as commit c099cf5.
Your commit was automatically rebased without conflicts. |
@AlanBateman Pushed as commit c099cf5. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Virtual threads doing blocking I/O rely on poller threads to unpark virtual threads when sockets are ready for I/O. Right now, the poller threads are dedicated platform threads that block waiting for I/O events. In some environments it would be better to have the poller thread be virtual threads so that handling of I/O events integrates better with the virtual thread scheduler and doesn't steal cycles from the carrier threads.
The changes to support this are straight forward but it has required refactoring the internal Poller class so the changes might look more than they actually are. The changes mean the Poller implementation supports two modes. The default is changed on Linux to use the "virtual thread poller" mode. The default on other platforms is to use platform threads as before. As part of the refactor, the so-called "indirect" mode with updater threads is removed. This mode came from experimenting in the loom repo a long time ago and probably should have been removed before integration.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/16243/head:pull/16243
$ git checkout pull/16243
Update a local copy of the PR:
$ git checkout pull/16243
$ git pull https://git.openjdk.org/jdk.git pull/16243/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 16243
View PR using the GUI difftool:
$ git pr show -t 16243
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/16243.diff
Webrev
Link to Webrev Comment