Linux NFS development
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Peng Tao <tao.peng@primarydata.com>
Cc: linux-nfs@vger.kernel.org,
	Trond Myklebust <trond.myklebust@primarydata.com>,
	Anna Schumaker <anna.schumaker@netapp.com>,
	Christoph Hellwig <hch@infradead.org>, Zach Brown <zab@zabbo.net>,
	Darren Hart <dvhart@linux.intel.com>,
	bfields@fieldses.org, Jeff Layton <jeff.layton@primarydata.com>,
	linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RFC 01/11] vfs: pull btrfs clone API to vfs layer
Date: Wed, 26 Aug 2015 11:59:43 +1000	[thread overview]
Message-ID: <20150826015943.GZ3902@dastard> (raw)
In-Reply-To: <20150826015034.GY3902@dastard>

On Wed, Aug 26, 2015 at 11:50:34AM +1000, Dave Chinner wrote:
> On Tue, Aug 25, 2015 at 11:33:39PM +0800, Peng Tao wrote:
> > Now that a few file systems are adding clone functionality, namingly
> > btrfs, NFS (later in the series) and XFS
> > (ttp://oss.sgi.com/archives/xfs/2015-06/msg00407.html), it makes sense
> > to pull the ioctl to common code.
> > 
> > Add vfs_file_clone_range() helper and .clone_range file operation interface
> > to allow underlying filesystems to clone between regular files.
> > 
> > The change in do_vfs_ioctl() is defered to next patch where btrfs
> > .clone_range is added, just so that we don't break btrfs CLONE ioctl
> > with this patch.
> > 
> > Cc: linux-btrfs@vger.kernel.org
> > Cc: linux-fsdevel@vger.kernel.org
> 
> Can you please cc the entire patch series to linux-fsdevel?
> 
> Spraying random patches from a larger series to different lists is
> not very nice - I can't really comment on this patch because I have
> no idea what context it is being proposed in, what the problem being
> solved is, how it is being used by existing filesystems, how it will
> be used by your new changes, etc.
> 
> You may have explained all this in patch 0 for the series, but
> that hasn't been cc'd to linux-fsdevel....

Also, proposed test infrastructure for the clone_range functionality
that Darrick is working on for XFS (and to validate existing btrfs
functionality):

http://oss.sgi.com/archives/xfs/2015-06/msg00479.html

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2015-08-26  1:59 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25 15:33 [PATCH RFC 00/11] NFS/NFSD: add NFSv42 COPY operation support Peng Tao
2015-08-25 15:33 ` [PATCH RFC 01/11] vfs: pull btrfs clone API to vfs layer Peng Tao
2015-08-26  1:40   ` Peng Tao
2015-08-26  1:50   ` Dave Chinner
2015-08-26  1:59     ` Dave Chinner [this message]
2015-08-26  4:09   ` Darrick J. Wong
2015-08-26  8:03     ` Peng Tao
2015-08-25 15:33 ` [PATCH RFC 02/11] vfs/btrfs: add .clone_range file operation Peng Tao
2015-08-26  8:01   ` David Sterba
2015-08-26  8:31     ` Peng Tao
2015-08-26 13:00       ` David Sterba
2015-08-26 13:07         ` Christoph Hellwig
2015-08-25 15:33 ` [PATCH RFC 03/11] nfs42: decode_layoutstats does not need res parameter Peng Tao
2015-08-25 16:04   ` Anna Schumaker
2015-08-25 15:33 ` [PATCH RFC 04/11] nfs42: remove unused declaration Peng Tao
2015-08-25 16:05   ` Anna Schumaker
2015-08-25 16:08     ` Peng Tao
2015-08-25 15:33 ` [PATCH RFC 05/11] nfs42: add CLONE xdr functions Peng Tao
2015-08-25 15:33 ` [PATCH RFC 06/11] nfs42: add CLONE proc functions Peng Tao
2015-08-25 15:33 ` [PATCH RFC 07/11] nfs42: add .copy_range file operation Peng Tao
2015-08-25 15:33 ` [PATCH RFC 08/11] nfs: get clone_blksize when probing fsinfo Peng Tao
2015-08-25 15:33 ` [PATCH RFC 09/11] nfs42: respect clone_blksize Peng Tao
2015-08-25 15:33 ` [PATCH RFC 10/11] nfsd: Pass filehandle to nfs4_preprocess_stateid_op() Peng Tao
2015-08-25 15:33 ` [PATCH RFC 11/11] NFSD: Implement the CLONE call Peng Tao
2015-08-25 22:09   ` J. Bruce Fields
2015-08-25 22:11   ` J. Bruce Fields
2015-08-26  1:33     ` Peng Tao
2015-08-25 15:42 ` [PATCH RFC 00/11] NFS/NFSD: add NFSv42 COPY operation support Peng Tao
2015-08-25 16:01   ` Anna Schumaker

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=20150826015943.GZ3902@dastard \
    --to=david@fromorbit.com \
    --cc=anna.schumaker@netapp.com \
    --cc=bfields@fieldses.org \
    --cc=dvhart@linux.intel.com \
    --cc=hch@infradead.org \
    --cc=jeff.layton@primarydata.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tao.peng@primarydata.com \
    --cc=trond.myklebust@primarydata.com \
    --cc=zab@zabbo.net \
    /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