Re: [RFC v0 4/4] nfs, nfsd: rough sys_copy_range and COPY support

[J. Bruce Fields]

On Wed, May 15, 2013 at 08:21:54PM +0000, Myklebust, Trond wrote:
> On Wed, 2013-05-15 at 16:19 -0400, J. Bruce Fields wrote:
> > On Tue, May 14, 2013 at 02:15:26PM -0700, Zach Brown wrote:
> > > This crude patch illustrates the simplest plumbing involved in
> > > supporting sys_call_range with the NFS COPY operation that's pending in
> > > the 4.2 draft spec.
> > > 
> > > The patch is based on a previous prototype that used the COPY op to
> > > implement sys_copyfileat which created a new file (based on the ocfs2
> > > reflink ioctl).  By contrast, this copies file contents between existing
> > > files.
> > > 
> > > There's still a lot of implementation and testing to do, but this can
> > > get discussion going.
> > 
> > I'm using:
> > 
> > 	git://github.com/loghyr/NFSv4.2
> > 
> > as my reference for the draft protocol.
> > 
> > On a quick skim, one thing this is missing before it complies is a
> > client implementation of CB_OFFLOAD: "If a client desires an
> > intra-server file copy, then it MUST support the COPY and CB_OFFLOAD
> > operations."
> 
> Note that Bryan is currently working on updating the NFS implementation
> to match the draft protocol.

OK, good.--b.
--
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/