Skip to content
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

write_buf/read_buf support ? (needed for FUSE_CAP_SPLICE_READ ?) #298

Open
touilleMan opened this issue Oct 2, 2024 · 0 comments
Open

Comments

@touilleMan
Copy link

Hi !

Unlike libfuse, it seems fuser doesn't expose write_buf/read_buf callbacks (only write/read are)

I'm by no mean a Fuse expert, but from what I've seen this write_buf/read_buf stuff is not part of the FUSE protocol but instead something internal to libfuse (as I haven't seen any opcode dedicated to it)

According to libfuse's documentation, write_buf must be defined to enable support of FUSE_CAP_SPLICE_READ.
So what does it means for fuser ?

On top of that, I wonder if this write_buf would allow doing zero-copy when doing the write asynchronously (as currently Filesystem::write takes a data: &[u8] parameter so the data must be copied in an owned buffer first if the write operation has to be done in a separated thread, see for instance )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant