Date: Wed, 19 Jun 2019 18:55:06 -0600 From: Alan Somers <asomers@freebsd.org> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: RFC: should a copy_file_range(2) syscall work across multiple file systems? Message-ID: <CAOtMX2je34OCuGG_B%2BiGF7NbwywOU_OupDArCjg_9tc5REUH_g@mail.gmail.com> In-Reply-To: <YTXPR01MB02853C73E79C0A5CFEE636E8DDE50@YTXPR01MB0285.CANPRD01.PROD.OUTLOOK.COM> References: <YTXPR01MB02853C73E79C0A5CFEE636E8DDE50@YTXPR01MB0285.CANPRD01.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 19, 2019 at 5:56 PM Rick Macklem <rmacklem@uoguelph.ca> wrote: > > I have been working on a copy_file_range(2) syscall for FreeBSD, which is meant > to be compatible with the Linux one. (Current patch is at > https://reviews.freebsd.org/D20584) > > One thing the current patch does do is allow the kernel copy to be done across > multiple file systems (ie. source and destination files on different file systems). > The Linux syscall *may* not allow this. The man page specifies EXDEV as an > error return, but discussion of the Linux syscall suggests that it may be (or has > already been) modified to work across multiple file systems. > > I thought that this would be a useful feature, but does require the default > code to be above the VOP_xxx() layer and *might* not be Linux compatible. > (The incompatibility would be working for cases where the Linux syscall might not.) > > So, should it work across multiple file systems? > rick I don't think there's anything wrong with it. Do it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2je34OCuGG_B%2BiGF7NbwywOU_OupDArCjg_9tc5REUH_g>