docs(design): macOS F_NOCACHE and writev fallback (#1657)#3724
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.
Summary
F_NOCACHEon the destination fd withwritev(2)for the buffered-write path. Targets the gap between today's plainBufWriter<File>on macOS and the longer-term kqueue backend in Adjust CI coverage gate and extend cross-platform builds #1385.docs/design/macos-kqueue-fast-io.mdSection 7.2) and fills in theWritevAsyncWriterbranch named in the AsyncFileWriter audit (Refactor module list client into modular structure #1655).fast_io(WritevWriter,WritevPolicy,--writev-macosflag), interaction with sparse mode (falls through toBufferedforSeek), comparison vs full kqueue (Adjust CI coverage gate and extend cross-platform builds #1385) anddispatch_io(Fix client module test visibility and import duplication #1653, completed), test plan against the existing macOS CI matrix, and open questions covering rename targets, threshold tuning,--inplace, SMB,fcopyfile, and AppleDouble (Align Windows cross-compile matrix with documentation #1907).Test plan