Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Steve French <smfrench@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>, Al Viro <viro@zeniv.linux.org.uk>,
	Peng Tao <tao.peng@primarydata.com>,
	Jeffrey Layton <jeff.layton@primarydata.com>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-btrfs@vger.kernel.org,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"linux-cifs@vger.kernel.org" <linux-cifs@vger.kernel.org>
Subject: Re: vfs: move btrfs clone ioctls to common code
Date: Wed, 2 Dec 2015 08:27:57 +0100	[thread overview]
Message-ID: <20151202072757.GB15839@lst.de> (raw)
In-Reply-To: <CAH2r5muW6=v6tx3BwXSYMgn7EZgzVANniebsxfwpdq9Y=0VcuA@mail.gmail.com>

Hi Steve,

we have two APIs in Linux:

 - the copy_file_range syscall which just is a "do a copy by any means"
 - the btrfs clone ioctls which have stricter semantics that very much
   expect a reflink-like operation

I plan to also wire up copy_file_range to try the clone_file_range method
first if available to make life easier for file systems, but as there isn't
any test coverage for that I don't dare to actually submit it yet.  I'll
send a compile tested only RFC for it when resending this series.

  reply	other threads:[~2015-12-02  7:27 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 2/5] locks: new locks_mandatory_area calling convention Christoph Hellwig
     [not found]   ` <1448563859-21922-3-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2015-11-30 22:38     ` J. Bruce Fields
     [not found]       ` <20151130223830.GB31564-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
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
     [not found] ` <1448563859-21922-1-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2015-11-26 18:50   ` [PATCH 1/5] cifs: implement clone_file_range operation Christoph Hellwig
     [not found]     ` <1448563859-21922-2-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2015-11-27 10:42       ` David Disseldorp
     [not found]         ` <20151127114232.5b367b7b-TzLh5lQYVSQb1SvskN2V4Q@public.gmane.org>
2015-11-30  9:02           ` 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
2015-12-01 22:48   ` Steve French
2015-12-02  7:27     ` Christoph Hellwig [this message]
     [not found]       ` <20151202072757.GB15839-jcswGhMUV9g@public.gmane.org>
2015-12-02 17:40         ` Steve French
2015-12-03 10:30           ` Christoph Hellwig
     [not found]             ` <20151203103035.GA15996-jcswGhMUV9g@public.gmane.org>
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=20151202072757.GB15839@lst.de \
    --to=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=smfrench@gmail.com \
    --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