From: Christoph Hellwig <hch@infradead.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel@vger.kernel.org, netdev@vger.kernel.org
Subject: getting rid of ->splice_write?
Date: Mon, 22 Sep 2014 10:30:53 -0700 [thread overview]
Message-ID: <20140922173053.GA13109@infradead.org> (raw)
Currently only /dev/null, fusedev and the socket code have a
splice_write implementation that isn't iter_file_splice_write, and
it seems like these three could easily be switched over if they
implemented a ->write_iter.
Similarly it seems to be like we could kill ->splice_read by
implementing an equivalent iteration over ->read_iter.
next reply other threads:[~2014-09-22 17:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 17:30 Christoph Hellwig [this message]
2014-11-05 18:49 ` getting rid of ->splice_write? Al Viro
2014-11-06 7:55 ` Christoph Hellwig
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=20140922173053.GA13109@infradead.org \
--to=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=netdev@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).