linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org
Subject: Re: [LSF/MM TOPIC] reverse splice
Date: Thu, 21 Feb 2019 06:28:42 -0800	[thread overview]
Message-ID: <20190221142842.GO12668@bombadil.infradead.org> (raw)
In-Reply-To: <CAJfpegusa=r+sdbsTx1ybq6FMKy5Zp=L=u7viRYbndYiRLJh9A@mail.gmail.com>

On Thu, Feb 21, 2019 at 01:56:11PM +0100, Miklos Szeredi wrote:
> rsplice would serve a similar purpose as splice, but in the other
> direction.  I.e. instead of operating on buffers filled with data, it
> would operate on empty buffers to be filled with data.  rsplice is to
> splice as read is to write.
> 
> data source -> splice -> data destination
> data destination -> rsplice -> data source
> 
> One use case would be zero-copy read in fuse.   Zero-copy writes work
> with plain splice: page cache pages or userspace buffers are passed
> through to the userspace filesystem server as pipe buffers and they
> can be directed wherever the filesystem wants.   The reverse doesn't
> work.  There's code to attempt stealing pages and inserting into the
> fuse page cache, but this is far from being as generic as the write
> path.
> 
> What do people think?  Is this crazy?  Are there major roadblocks for
> implementation?  Would this have any other use cases?

This was something I was interested in last year for a project at my
then-employer.  It's not something I'm interested in right now, but I
could imagine it becoming interesting to me again fairly rapidly.

It's one of those projects I have to think very hard about and I don't
have the spare cycles to do that today.  So I think it should be done,
but I should probably stay focused on my other projects right now.

  reply	other threads:[~2019-02-21 14:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-21 12:56 [LSF/MM TOPIC] reverse splice Miklos Szeredi
2019-02-21 14:28 ` Matthew Wilcox [this message]
2019-02-21 14:29 ` Matthew Wilcox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190221142842.GO12668@bombadil.infradead.org \
    --to=willy@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=miklos@szeredi.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).