Re: [PATCH 0/3] vmsplice: make vmsplice a trivial wrapper for preadv2/pwritev2
Miklos Szeredi <[email protected]>
| Newsgroups | org.kernel.vger.linux-api,dev.linux.lists.fuse-devel,dev.linux.lists.patches,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-kernel,org.kernel.vger.netdev,org.kvack.linux-mm |
|---|---|
| Message-ID | <CAJfpegtH-E79D-3UL=pPv-QqJk6C4ODXLLZSAjzQJwSSeqqS-A@mail.gmail.com> |
On Mon, 1 Jun 2026 at 19:33, Al Viro <[email protected]> wrote: > > On Mon, Jun 01, 2026 at 10:17:23AM -0700, Linus Torvalds wrote: > > > TLDR: maybe we could ghet rid of "f_op->splice_read". *That* would be > > a big simplification. > > FUSE might be interesting - fuse_dev_splice_read() and its ilk. > Communications between the kernel and fuse server at least used to > seriously want that, so that would be one place to look for unhappy > userland... > > splice-related logics in fs/fuse/dev.c is interesting; another place > like this is kernel/trace/, but I'm less familiar with that one. [Cc: Joanne, fuse-devel] I'd favor simplification, but care is needed to not regress performance. Joanne might be in a better position to say something about relative performance of various transport modes in fuse. Thanks, Miklos