From: Chuck Lever <cel@citi.umich.edu>
To: Trond Myklebust <trond.myklebust@fys.uio.no>,
Christoph Hellwig <hch@infradead.org>
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 14:12:03 -0500 [thread overview]
Message-ID: <44205003.8070702@citi.umich.edu> (raw)
In-Reply-To: <1142967981.7987.92.camel@lade.trondhjem.org>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
Trond Myklebust wrote:
> As I said in my other posting, I believe Chuck's changes are relatively
> orthogonal to what you want to do: they neither make the low-level
> plumbing better or worse for readv()/writev().
>
> We'd be happy to work with you in the run-up to 2.6.18 to add
> multi-segment support for the existing patchsets. It makes more sense to
> me to append that functionality to the existing patchsets rather than
> trigger a complete rewrite (and thus have a sh_tload more code to
> retest).
after i reviewed this work with zach last summer, he and i also agreed
that it would be best if i did this work after the generic changes are
integrated -- so he wouldn't have to work on, and possibly break, the
NFS client.
i have been watching the multi-segment iovec work since then, and fully
intended to add the support for readv/writev aio in the NFS direct path
when the generic support becomes available.
[-- 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 19:12 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
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 [this message]
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=44205003.8070702@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®