Reorder limiter test support exports#1861
Merged
Merged
Conversation
4 tasks
oferchen
added a commit
that referenced
this pull request
Apr 29, 2026
* docs(transport): investigate splice()/vmsplice() for SSH stdio (#1860) Audit confirms upstream rsync 3.4.1 does not use splice. Identifies the file-to-pipe (sender) and pipe-to-file (receiver) edges as the only realistic targets for zero-copy on the SSH stdio path, since the parent does not own the SSH child's TCP socket. Documents the multiplex envelope constraint (4-byte header + 24-bit payload) and proposes a three-phase plan: payload splice on the sender, payload splice on the receiver, and vmsplice for the header ring. Risks cover vmsplice page lifetime, SPLICE_F_NONBLOCK semantics, EPIPE on closed peers, and interaction with --bwlimit. Adds docs/perf-roadmap.md as the index. * bench(fast_io): add splice_pipe benchmark skeleton (#1860) Provides the criterion baseline for the SSH-stdio splice investigation. The Linux body runs a real read+write_all loop from a temp file through a drained pipe at three sizes (64 KiB, 1 MiB, 16 MiB), establishing the comparison point for the future splice driver. The splice_baseline slot is a placeholder that records a constant for now; follow-up #1861 wires the real fast_io::splice_pipe driver into that slot. Non-Linux targets compile to a no-op group so cargo bench succeeds on macOS and Windows.
oferchen
added a commit
that referenced
this pull request
May 1, 2026
* docs(transport): investigate splice()/vmsplice() for SSH stdio (#1860) Audit confirms upstream rsync 3.4.1 does not use splice. Identifies the file-to-pipe (sender) and pipe-to-file (receiver) edges as the only realistic targets for zero-copy on the SSH stdio path, since the parent does not own the SSH child's TCP socket. Documents the multiplex envelope constraint (4-byte header + 24-bit payload) and proposes a three-phase plan: payload splice on the sender, payload splice on the receiver, and vmsplice for the header ring. Risks cover vmsplice page lifetime, SPLICE_F_NONBLOCK semantics, EPIPE on closed peers, and interaction with --bwlimit. Adds docs/perf-roadmap.md as the index. * bench(fast_io): add splice_pipe benchmark skeleton (#1860) Provides the criterion baseline for the SSH-stdio splice investigation. The Linux body runs a real read+write_all loop from a temp file through a drained pipe at three sizes (64 KiB, 1 MiB, 16 MiB), establishing the comparison point for the future splice driver. The splice_baseline slot is a placeholder that records a constant for now; follow-up #1861 wires the real fast_io::splice_pipe driver into that slot. Non-Linux targets compile to a no-op group so cargo bench succeeds on macOS and Windows.
oferchen
added a commit
that referenced
this pull request
May 5, 2026
* docs(transport): investigate splice()/vmsplice() for SSH stdio (#1860) Audit confirms upstream rsync 3.4.1 does not use splice. Identifies the file-to-pipe (sender) and pipe-to-file (receiver) edges as the only realistic targets for zero-copy on the SSH stdio path, since the parent does not own the SSH child's TCP socket. Documents the multiplex envelope constraint (4-byte header + 24-bit payload) and proposes a three-phase plan: payload splice on the sender, payload splice on the receiver, and vmsplice for the header ring. Risks cover vmsplice page lifetime, SPLICE_F_NONBLOCK semantics, EPIPE on closed peers, and interaction with --bwlimit. Adds docs/perf-roadmap.md as the index. * bench(fast_io): add splice_pipe benchmark skeleton (#1860) Provides the criterion baseline for the SSH-stdio splice investigation. The Linux body runs a real read+write_all loop from a temp file through a drained pipe at three sizes (64 KiB, 1 MiB, 16 MiB), establishing the comparison point for the future splice driver. The splice_baseline slot is a placeholder that records a constant for now; follow-up #1861 wires the real fast_io::splice_pipe driver into that slot. Non-Linux targets compile to a no-op group so cargo bench succeeds on macOS and Windows.
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
Testing
https://chatgpt.com/codex/tasks/task_e_69057f9b5a948323b4697f857cf4d143