From: Christoph Hellwig <hch@infradead.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net,
nfsv4@linux-nfs.org
Subject: Re: [NFS] [GIT] NFS client update for 2.6.16
Date: Tue, 21 Mar 2006 17:46:34 +0000 [thread overview]
Message-ID: <20060321174634.GA15827@infradead.org> (raw)
In-Reply-To: <1142961077.7987.14.camel@lade.trondhjem.org>
> commit 47989d7454398827500d0e73766270986a3b488f
> Author: Chuck Lever <cel@netapp.com>
> 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.
next prev parent reply other threads:[~2006-03-21 17:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 17:11 [GIT] NFS client update for 2.6.16 Trond Myklebust
2006-03-21 17:11 ` Trond Myklebust
2006-03-21 17:46 ` Christoph Hellwig [this message]
2006-03-21 18:03 ` [NFS] " Chuck Lever
2006-03-21 18:03 ` Chuck Lever
2006-03-21 18:55 ` Christoph Hellwig
2006-03-21 18:08 ` Trond Myklebust
2006-03-21 18:08 ` Trond Myklebust
2006-03-21 18:57 ` Christoph Hellwig
2006-03-21 18:57 ` Christoph Hellwig
2006-03-21 19:06 ` Trond Myklebust
2006-03-21 19:06 ` Trond Myklebust
2006-03-21 19:12 ` Chuck Lever
2006-03-21 19:12 ` Chuck Lever
2006-03-22 10:30 ` Christoph Hellwig
2006-03-22 10:30 ` [NFS] " Christoph Hellwig
2006-03-22 11:35 ` Trond Myklebust
2006-03-22 11:35 ` Trond Myklebust
2006-03-21 18:58 ` Trond Myklebust
2006-03-21 18:58 ` Trond Myklebust
2006-03-22 10:25 ` Christoph Hellwig
2006-03-22 10:25 ` Christoph Hellwig
2006-03-21 17:50 ` Jeff Garzik
2006-03-21 18:12 ` Trond Myklebust
2006-03-21 18:12 ` Trond Myklebust
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=20060321174634.GA15827@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=nfsv4@linux-nfs.org \
--cc=torvalds@osdl.org \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.