mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Christoph Hellwig <hch@infradead.org>
Cc: Chuck Lever <cel@citi.umich.edu>,
	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: Wed, 22 Mar 2006 06:35:12 -0500	[thread overview]
Message-ID: <1143027313.12871.27.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20060322103044.GB7025@infradead.org>

On Wed, 2006-03-22 at 10:30 +0000, Christoph Hellwig wrote:
> On Tue, Mar 21, 2006 at 02:12:03PM -0500, Chuck Lever wrote:
> > 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.
> 
> 
> we agreed to not add another set of methods but rather consolidate the
> existing two sets of aio and vectored methods into one.  So to merge the
> core support all users including nfs need to be updated.  the last wip
> patchset is posted in the at:
> 
> 	http://marc.theaimsgroup.com/?l=linux-kernel&m=114177713027505&w=2
> 	http://marc.theaimsgroup.com/?l=linux-kernel&m=114177739515518&w=2
> 	http://marc.theaimsgroup.com/?l=linux-kernel&m=114177739313588&w=2
> 	http://marc.theaimsgroup.com/?l=linux-kernel&m=114177739407636&w=2
> 
> any nfs work should happen ontop of that.
> 
> I'm sill the opinion removing the iovec arguments isn't helpfull, but
> it's your code and if you think it helps you move forwarg go ahead with
> this.

Adding multi-segment support on top of this is not going to be a huge
job since the new code already does a form of multi-segment tracking in
the lower layers. By that I mean that it has to convert an arbitrarily
sized user buffer into a series of asynchronous NFS requests to be put
on the wire and then track them until they have completed. That is
pretty much all you have to do for the multi-iovec case too.

Cheers,
  Trond


  reply	other threads:[~2006-03-22 11:35 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
2006-03-22 10:30           ` Christoph Hellwig
2006-03-22 11:35             ` Trond Myklebust [this message]
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=1143027313.12871.27.camel@lade.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=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 \
    /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®