From: Christoph Hellwig <hch@lst.de>
To: dsterba@suse.cz, Christoph Hellwig <hch@lst.de>,
linux-btrfs@vger.kernel.org, Andy Lavr <andy.lavr@gmail.com>
Subject: Re: [PATCH] btrfs: wire up iter_file_splice_write
Date: Thu, 9 Jul 2020 19:26:34 +0200 [thread overview]
Message-ID: <20200709172634.GA17914@lst.de> (raw)
In-Reply-To: <20200709172428.GD15161@twin.jikos.cz>
On Thu, Jul 09, 2020 at 07:24:28PM +0200, David Sterba wrote:
> On Thu, Jul 09, 2020 at 06:22:06PM +0200, Christoph Hellwig wrote:
> > btrfs implements the iter_write op and thus can use the more efficient
> > iov_iter based splice implementation. For now falling back to the less
> > efficient default is pretty harmless, but I have a pending series that
> > removes the default, and thus would cause btrfs to not support splice
> > at all.
>
> Do you want this patch to go in this cycle? I have some more patches
> queued and don't mind adding it if it makes development of your patchset
> easier.
That would be great.
prev parent reply other threads:[~2020-07-09 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 16:22 [PATCH] btrfs: wire up iter_file_splice_write Christoph Hellwig
2020-07-09 17:24 ` David Sterba
2020-07-09 17:26 ` Christoph Hellwig [this message]
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=20200709172634.GA17914@lst.de \
--to=hch@lst.de \
--cc=andy.lavr@gmail.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
/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).