From: Chris Mason <clm@fb.com>
To: Christoph Hellwig <hch@lst.de>
Cc: <viro@zeniv.linux.org.uk>, <tao.peng@primarydata.com>,
<jeff.layton@primarydata.com>, <linux-fsdevel@vger.kernel.org>,
<linux-btrfs@vger.kernel.org>, <linux-nfs@vger.kernel.org>,
<linux-cifs@vger.kernel.org>
Subject: Re: vfs: move btrfs clone ioctls to common code
Date: Tue, 1 Dec 2015 12:09:20 -0500 [thread overview]
Message-ID: <20151201170920.GB8918@ret.masoncoding.com> (raw)
In-Reply-To: <1448563859-21922-1-git-send-email-hch@lst.de>
On Thu, Nov 26, 2015 at 07:50:54PM +0100, Christoph Hellwig wrote:
> This patch set moves the existing btrfs clone ioctls that other file
> system have started to implement to common code, and allows the NFS
> server to export this functionality to remote systems.
>
> This work is based originally on my NFS CLONE prototype, which reused
> code from Anna Schumaker's NFS COPY prototype, as well as various
> updates from Peng Tao to this code.
>
> The patches are also available as a git branch and on gitweb:
>
> git://git.infradead.org/users/hch/pnfs.git clone-for-viro
Thanks Christoph, this looks fine to me.
-chris
next prev parent reply other threads:[~2015-12-01 17:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 18:50 vfs: move btrfs clone ioctls to common code Christoph Hellwig
2015-11-26 18:50 ` [PATCH 1/5] cifs: implement clone_file_range operation Christoph Hellwig
2015-11-27 10:42 ` David Disseldorp
2015-11-30 9:02 ` Christoph Hellwig
2015-11-26 18:50 ` [PATCH 2/5] locks: new locks_mandatory_area calling convention Christoph Hellwig
2015-11-30 22:38 ` J. Bruce Fields
2015-12-01 7:37 ` Christoph Hellwig
2015-11-26 18:50 ` [PATCH 3/5] vfs: pull btrfs clone API to vfs layer Christoph Hellwig
2015-11-26 18:50 ` [PATCH 4/5] nfsd: Pass filehandle to nfs4_preprocess_stateid_op() Christoph Hellwig
2015-11-26 18:50 ` [PATCH 5/5] nfsd: implement the NFSv4.2 CLONE operation Christoph Hellwig
2015-11-30 22:56 ` vfs: move btrfs clone ioctls to common code J. Bruce Fields
2015-12-01 17:09 ` Chris Mason [this message]
2015-12-01 22:48 ` Steve French
2015-12-02 7:27 ` Christoph Hellwig
2015-12-02 17:40 ` Steve French
2015-12-03 10:30 ` Christoph Hellwig
2015-12-03 19:28 ` Steve French
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=20151201170920.GB8918@ret.masoncoding.com \
--to=clm@fb.com \
--cc=hch@lst.de \
--cc=jeff.layton@primarydata.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tao.peng@primarydata.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).