Set IOSQE_ASYNC for some operations #123
Merged
Conversation
This file contains 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
For operations which we don't expect to complete the first time the submission event is processed we let the kernel know not to attempt do non-blocking operation first, but instead do it in an async manner from the start. We do this for: * such as receiving process signal, * accepting connections, and * polling.
The entire crate is asynchronous, so no point in this duplication.
Sometime the accept operation was started, which means we get 1, other time the operation hasn't start yet, which means we get 0.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For operations which we don't expect to complete the first time the
submission event is processed we let the kernel know not to attempt do
non-blocking operation first, but instead do it in an async manner from
the start.
We do this for: