Fix handling of read_nonblock.#143
Merged
Merged
Conversation
ioquatix
force-pushed
the
io_uring-non-blocking-read
branch
2 times, most recently
from
e06a080 to
2a0fde4
Compare
ioquatix
force-pushed
the
io_uring-non-blocking-read
branch
from
2a0fde4 to
237810b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
io_uringblocks even when the length is zero and the IO is set to non-blocking mode. This causedunicornin async mode to hang, because it depends on this behaviour. It worked fine withEPollbut notURing.See socketry/async-examples#15 for more context.
Types of Changes
Contribution