From: Trond Myklebust Subject: Re: [NFS] [GIT] NFS client update for 2.6.16 Date: Tue, 21 Mar 2006 13:08:52 -0500 Message-ID: <1142964532.7987.61.camel@lade.trondhjem.org> References: <1142961077.7987.14.camel@lade.trondhjem.org> <20060321174634.GA15827@infradead.org> Mime-Version: 1.0 Content-Type: text/plain Cc: nfsv4@linux-nfs.org, Linus Torvalds , nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org Return-path: To: Christoph Hellwig In-Reply-To: <20060321174634.GA15827@infradead.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nfsv4-bounces@linux-nfs.org Errors-To: nfsv4-bounces@linux-nfs.org List-ID: On Tue, 2006-03-21 at 17:46 +0000, Christoph Hellwig wrote: > > commit 47989d7454398827500d0e73766270986a3b488f > > Author: Chuck Lever > > Date: Mon Mar 20 13:44:32 2006 -0500 > > > > NFS: remove support for multi-segment iovs in the direct write path > > > > Eliminate the persistent use of automatic storage in all parts of the > > NFS client's direct write path to pave the way for introducing support > > for aio against files opened with the O_DIRECT flag. > > NACK. We have patches pending that consolidate ->aio_read/write and > ->read/writev into one operation. this change is completely counterproductive > towards that goal which has been discussed on -fsdevel for a while. How so? The interface is _exactly_ the same as before. We never had support for multiple iovecs in O_DIRECT, but were passing around a single iovec entry deep into code that couldn't care less. Cheers, Trond