From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christoph Hellwig <hch@infradead.org>
Subject: getting rid of ->splice_write?
Date: Mon, 22 Sep 2014 10:30:53 -0700
Message-ID: <20140922173053.GA13109@infradead.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Miklos Szeredi <miklos@szeredi.hu>, linux-fsdevel@vger.kernel.org,
	netdev@vger.kernel.org
To: Al Viro <viro@zeniv.linux.org.uk>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from bombadil.infradead.org ([198.137.202.9]:58452 "EHLO
	bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1754291AbaIVRa4 (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Mon, 22 Sep 2014 13:30:56 -0400
Content-Disposition: inline
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

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.