docs(audits): io_uring fixed-buffer registration coverage (#2118)#3899
Merged
Conversation
Document which io_uring read/write SQEs use READ_FIXED/WRITE_FIXED today, which still pay per-op page pinning, and the bench plan plus recommendation for the >= 64 KiB hot path.
github-actions
Bot
added
the
documentation
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
READ_FIXED/WRITE_FIXED, which still pay per-op page pinning, and where the missing wiring matters for >= 64 KiB workloads.IoUringDiskBatchand the delta-apply basis read as the two largest uncovered slabs of hot-path I/O.get_user_pages_fastskip).Test plan