[GIT PULL] man: Explain transfer size limits#1571
Merged
axboe merged 5 commits intoaxboe:masterfrom Apr 24, 2026
Merged
Conversation
Tweak the discussion text from e65a2a0, and replicate it across all read()-based functions. Linux's read() function has special limitations, so the text in these functions should be visibly different to the blurb elsewhere. To achieve that, io_uring_cqe's result code is only discussed explicitly in this commit. Based on a discussion in axboe#1570 Signed-off-by: Andrew Sayers <andrew-github.com@pileofstuff.org>
Based on a discussion in axboe#1570 Signed-off-by: Andrew Sayers <andrew-github.com@pileofstuff.org>
Based on a discussion in axboe#1570 Signed-off-by: Andrew Sayers <andrew-github.com@pileofstuff.org>
io_uring_buf_ring_add(3) does not transfer data, but people reading that page are likely to appreciate a hint about maximum buffer sizes. A quick test shows splice(3) and tee(3) don't return much data per call. If a user saw text in io_uring_prep_splice(3) or io_uring_prep_tee(3) that looked just like the other man pages, they would have the right to be surprised when they found the functions behaved differently. The man pages for splice and tee don't mention any particular limits, so these man pages just say "limits as low as 65536 have been observed" - specific enough to alert the reader, but vague enough not to imply undue certainty. Based on a discussion in axboe#1570 Signed-off-by: Andrew Sayers <andrew-github.com@pileofstuff.org>
Signed-off-by: Andrew Sayers <andrew-github.com@pileofstuff.org>
Owner
|
Good stuff, thanks! |
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.
This is the promised generalisation of #1570, explaining the transfer size limits for various functions.
I think I've found all the relevant pages now, but please let me know if I missed anything.
git request-pull output:
By submitting this pull request, I acknowledge that: