Björn Jacke bj at sernet.de
Wed May 31 14:29:10 UTC 2017

On 2017-05-11 at 00:25 -0700 Christoph Hellwig sent off:
> As I haven't seen any follow up here:  Can we please move the
> IOC_CLONE_RANGE support out of the btrfs module as it's a general Linux
> API, and can't just be replace with copy_file_range?

from what I can tell copy_file_range? does what we need, doesn't it? And it has
support for several filesystems already while IOC_CLONE_RANGE might only be
supported for more filesystems in the future (maybe). David: I can send updated
patch the next days unless we say for some reason that copy_file_range isn't
the way we want to go anyway.

SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
  ☎ +49-551-370000-0, ℻ +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20170531/ccffb7ea/signature.sig>

More information about the samba-technical mailing list