-
Notifications
You must be signed in to change notification settings - Fork 216
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
8307425: Socket input stream read burns CPU cycles with back-to-back poll(0) calls #1341
Conversation
Hi @roy-soumadipta, welcome to this OpenJDK project and thanks for contributing! We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user roy-soumadipta" as summary for the issue. If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing |
This backport pull request has now been updated with issue from the original commit. |
/covered |
Thank you! Please allow for a few business days to verify that your employer has signed the OCA. Also, please note that pull requests that are pending an OCA check will not usually be evaluated, so your patience is appreciated! |
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, 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.
Looks fine to me. Please ask @olivergillespie to tag the issue for maintainer approval.
@roy-soumadipta 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 10 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 As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@shipilev) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@roy-soumadipta |
You should have waited with /integrate until the backport is approved via JBS label. |
And also please enable and run GHA for a basic verification of this fix. Thanks. |
Thanks, OpenJDK GHA is now running. Workflows were enabled after the PR was raised and didn't run automatically. Apologies for the early /integrate, was not aware of this. |
Thanks. Backport is approved and somebody can sponsor it now. |
@roy-soumadipta, could you please go to GHA checks and re-schedule the GHA run? I'd like to make sure it is completely green. Then I can sponsor. |
Hi @shipilev, I tried to re-run the failed jobs quite a few times and the failure seems to be unrelated to the change.
Is there any suggested course of action for this? |
This is probably a GHA infra failure. I see you have another run in cooking, let's see how that one does. |
@shipilev all the checks have passed. The PR is now ready to sponsor. |
Good! /sponsor |
Going to push as commit 7610862.
Your commit was automatically rebased without conflicts. |
@shipilev @roy-soumadipta Pushed as commit 7610862. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Backport 73ac710533a45bf5ba17f308aa49556b877b8bf9 to JDK 17u.
Backporting the fix for https://bugs.openjdk.org/browse/JDK-8307425 merged as part of openjdk/jdk#13798
Almost all the hunks were rejected. DatagramChannelImpl doesn't override park in jdk17, and hence has been left unchanged. Respective hunks for NioSocketImpl and SelChImpl were not cleanly applied due to the difference in how park is implemented for the respective classes between openjdk/jdk17u and openjdk/jdk. In openjdk/jdk in park, current thread is checked to be virtual or not and if that equates to true Poller.poll is used instead of Net.poll.
NioSocketImpl.java in openjdk/jdk17u:
NioSocketImpl.java in openjdk/jdk:
SelChImpl.java in openjdk/jdk17u:
SelChImpl.java in openjdk/jdk17u:
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/1341/head:pull/1341
$ git checkout pull/1341
Update a local copy of the PR:
$ git checkout pull/1341
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/1341/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 1341
View PR using the GUI difftool:
$ git pr show -t 1341
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/1341.diff
Webrev
Link to Webrev Comment