-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vectored IO for files #266
Labels
F-feature-request
feature request
Comments
For context, this issue arises from opendal's efforts to integrate with monoio-fs: apache/opendal#4552 |
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Vectored IO for files is neither implemented directly nor through
AsyncWriteRent
andAsyncReadRent
traits.Describe the solution you'd like
File
struct.AsyncWriteRent
andAsyncReadRent
traits forFile
struct.Describe alternatives you've considered
It is possible to emulate vectored write through multiple single writes, but that missed the point of using io_uring.
Additional context
io_uring provides an option to specify offset for vectored IO but monoio's
WriteVec
andReadVec
op structs don't support it. We could add a new vectored IO op struct with offset or manipulate current op struct definition.For tcp and unix sockets, vectored IO is implemented through
AsyncWriteRent
andAsyncReadRent
.Not implementing
AsyncWriteRent
andAsyncReadRent
also causesBufWriter
andBufReader
to be unusable for files. See #133.The text was updated successfully, but these errors were encountered: