Re: [NFS] [GIT] NFS client update for 2.6.16

[Trond Myklebust]

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/