Repository navigation
Document multishot accept and peer-address ownership. - #42
Merged
Merged
Conversation
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
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.
Capture the proposed
SocketAcceptMulti::socket_accept_multiinterface as an owned subscription yielding accepted sockets, with explicit peer-address lookup when needed.Explain why io_uring multishot accept's shared address output cannot provide a reliable address for each CQE, including the overwrite sequence when multiple accepts complete before userspace processes them. Record the bounded-delivery, cancellation, retirement, rearming, and undelivered-socket ownership questions still to settle. Distinguish repeated results from prepared chains, pool-backed receives, and the hypothetical
with_previous_bufferdependency.The interface remains proposed and unimplemented; this PR changes only
crates/executor/design.md.