docs(design): async daemon impact on io_uring integration (#1595)#4217
Merged
Conversation
Evaluate the four candidate shapes for integrating io_uring with the async daemon runtime and recommend keeping io_uring synchronous, with session-granularity spawn_blocking as the only async/sync boundary.
github-actions
Bot
added
the
documentation
This was referenced May 17, 2026
oferchen
added a commit
that referenced
this pull request
May 17, 2026
Restructure the SEND_ZC design doc around the explicit 7-section scope: current send path with file:line citations across daemon, transfer, and rsync_io; SEND_ZC semantics with the two-CQE notification model; registered-buffer ownership; kernel-6.0 runtime probe via IORING_REGISTER_PROBE; loopback + small-file bench plan; recommendation to defer until the daemon TCP wiring (#1876) lands; and cross-references to #4217 / #4218 / #4220 / #2243.
oferchen
added a commit
that referenced
this pull request
May 18, 2026
Restructure the SEND_ZC design doc around the explicit 7-section scope: current send path with file:line citations across daemon, transfer, and rsync_io; SEND_ZC semantics with the two-CQE notification model; registered-buffer ownership; kernel-6.0 runtime probe via IORING_REGISTER_PROBE; loopback + small-file bench plan; recommendation to defer until the daemon TCP wiring (#1876) lands; and cross-references to #4217 / #4218 / #4220 / #2243.
oferchen
added a commit
that referenced
this pull request
May 18, 2026
Restructure the SEND_ZC design doc around the explicit 7-section scope: current send path with file:line citations across daemon, transfer, and rsync_io; SEND_ZC semantics with the two-CQE notification model; registered-buffer ownership; kernel-6.0 runtime probe via IORING_REGISTER_PROBE; loopback + small-file bench plan; recommendation to defer until the daemon TCP wiring (#1876) lands; and cross-references to #4217 / #4218 / #4220 / #2243.
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.
Summary
docs/design/async-iouring-integration-eval.md, the focuseddecision-shaped successor to
docs/design/async-io-uring-impact.mdfor task Switch flate2 to the Rust backend for cross builds #1595.
tokio-uring,session-granularity
spawn_blocking, tokio default reactor +AsyncFd, strict-sync isolation) against oc-rsync's currentio_uring usage in
crates/fast_io/src/io_uring/.boundary once per session via
spawn_blocking, in line with thebridge contract in docs(design): spawn_blocking bridge for rayon work in async daemon (#1751) #4196 and the runtime rule in docs(design): async migration plan with incremental adoption strategy (#1594) #4186.
Test plan
cargo fmt --allclean.Ensure daemon fallback obeys disable overrides #1876.