On Wed, Dec 02, 2015 at 11:40:13AM -0600, Steve French wrote:
> If the copy_file_range is allowed to use any offload mechanism then
> cifs.ko could be changed as follows, to fallback among the three
> possible mechanisms depending on what the target supports.
How reliable are the fallbacks? E.g.
On Thu, Dec 3, 2015 at 4:30 AM, Christoph Hellwig wrote:
> On Wed, Dec 02, 2015 at 11:40:13AM -0600, Steve French wrote:
>> If the copy_file_range is allowed to use any offload mechanism then
>> cifs.ko could be changed as follows, to fallback among the three
>> possible mechanisms
On Wed, Dec 2, 2015 at 1:27 AM, Christoph Hellwig wrote:
> 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
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
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
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
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
Hi all,
This patchset moves BTRFS_IOC_CLONE/BTRFS_IOC_CLONE_RANGE to common vfs
layer and adds NFS42 CLONE support to knfsd.
It is based on top of Trond's linux-next branch (a85240d254) and Anna's latest
sys_copy_file_range work (v7).
With this, btrfs/cifs/nfs all handle CLONE/CLONE_RANGE