From: Chuck Lever <cel@citi.umich.edu>
To: Christoph Hellwig <hch@infradead.org>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
nfsv4@linux-nfs.org, Linus Torvalds <torvalds@osdl.org>,
nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [NFS] [GIT] NFS client update for 2.6.16
Date: Tue, 21 Mar 2006 13:03:47 -0500 [thread overview]
Message-ID: <44204003.6090700@citi.umich.edu> (raw)
In-Reply-To: <20060321174634.GA15827@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
Christoph Hellwig wrote:
>>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.
and when do you expect these changes to be integrated? we've had this
implementation for almost a year, and zach brown has reviewed it. we
discussed the aio_read/readv change with him and he agreed that this
should go in now.
we have major customers who are demanding this functionality now, and
can support the reimplementation whenever you guys get your aio act
together.
[-- Attachment #2: cel.vcf --]
[-- Type: text/x-vcard, Size: 451 bytes --]
begin:vcard
fn:Chuck Lever
n:Lever;Charles
org:Network Appliance, Incorporated;Open Source NFS Client Development
adr:535 West William Street, Suite 3100;;Center for Information Technology Integration;Ann Arbor;MI;48103-4943;USA
email;internet:cel@citi.umich.edu
title:Member of Technical Staff
tel;work:+1 734 763-4415
tel;fax:+1 734 763 4434
tel;home:+1 734 668-1089
x-mozilla-html:FALSE
url:http://troy.citi.umich.edu/u/cel/
version:2.1
end:vcard
next prev parent reply other threads:[~2006-03-21 18:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 17:11 Trond Myklebust
2006-03-21 17:46 ` [NFS] " Christoph Hellwig
2006-03-21 18:03 ` Chuck Lever [this message]
2006-03-21 18:55 ` Christoph Hellwig
2006-03-21 18:08 ` Trond Myklebust
2006-03-21 18:57 ` Christoph Hellwig
2006-03-21 19:06 ` Trond Myklebust
2006-03-21 19:12 ` Chuck Lever
2006-03-22 10:30 ` Christoph Hellwig
2006-03-22 11:35 ` Trond Myklebust
2006-03-21 18:58 ` Trond Myklebust
2006-03-22 10:25 ` Christoph Hellwig
2006-03-21 17:50 ` Jeff Garzik
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=44204003.6090700@citi.umich.edu \
--to=cel@citi.umich.edu \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®