From: Christoph Hellwig <hch@infradead.org>
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>
Subject: Re: [PATCH v2 0/8] nfs: minor cleanups and NFSv42 CLONE support
Date: Sun, 26 Jul 2015 09:59:58 -0700 [thread overview]
Message-ID: <20150726165958.GA24512@infradead.org> (raw)
In-Reply-To: <1436778368-65447-1-git-send-email-tao.peng@primarydata.com>
How is your progress on the server side patches to allow testing this?
Also can you move the btrfs ioctls to the VFS and dispatch them through
a file operation?
And please add Zack and Darren to the Cc list as they involved with
local filesystem cloning, thanks!
next prev parent reply other threads:[~2015-07-26 16:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 9:06 [PATCH v2 0/8] nfs: minor cleanups and NFSv42 CLONE support Peng Tao
2015-07-13 9:06 ` [PATCH v2 1/8] nfs42: decode_layoutstats does not need res parameter Peng Tao
2015-07-13 9:06 ` [PATCH v2 2/8] nfs42: remove unused declaration Peng Tao
2015-07-13 9:06 ` [PATCH v2 3/8] nfs42: add CLONE xdr functions Peng Tao
2015-07-13 9:06 ` [PATCH v2 4/8] nfs42: add CLONE proc functions Peng Tao
2015-07-13 9:06 ` [PATCH v2 5/8] nfs42: add NFS_IOC_CLONE ioctl Peng Tao
2015-07-13 13:53 ` Anna Schumaker
2015-07-13 15:46 ` Peng Tao
2015-07-13 9:06 ` [PATCH v2 6/8] nfs: get clone_blksize when probing fsinfo Peng Tao
2015-07-13 9:06 ` [PATCH v2 7/8] nfs42: respect clone_blksize Peng Tao
2015-07-13 9:06 ` [PATCH v2 8/8] nfs42: add NFS_IOC_CLONE_RANGE ioctl Peng Tao
2015-07-26 16:59 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-07-13 9:03 [PATCH v2 0/8] nfs: minor cleanups and NFSv42 CLONE support Peng Tao
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=20150726165958.GA24512@infradead.org \
--to=hch@infradead.org \
--cc=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=tao.peng@primarydata.com \
--cc=trond.myklebust@primarydata.com \
/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