Alan Somers wrote:
>On Fri, Jul 5, 2019 at 9:11 AM Rick Macklem wrote:
>>
>> Alan Somers wrote:
>> >On Thu, Jul 4, 2019 at 6:38 PM Rick Macklem wrote:
>> >>
>> >> I have a little program for testing the copy_file_range(2) syscall I've
>> >> been
>> >> working on. (The current version is
On Fri, Jul 5, 2019 at 9:11 AM Rick Macklem wrote:
>
> Alan Somers wrote:
> >On Thu, Jul 4, 2019 at 6:38 PM Rick Macklem wrote:
> >>
> >> I have a little program for testing the copy_file_range(2) syscall I've
> >> been
> >> working on. (The current version is attached, in case anyone is
> >>
Alan Somers wrote:
>On Thu, Jul 4, 2019 at 6:38 PM Rick Macklem wrote:
>>
>> I have a little program for testing the copy_file_range(2) syscall I've been
>> working on. (The current version is attached, in case anyone is interested.)
>>
>> It take a few minutes to run on a slow system and uses
On Thu, Jul 4, 2019 at 6:38 PM Rick Macklem wrote:
>
> I have a little program for testing the copy_file_range(2) syscall I've been
> working on. (The current version is attached, in case anyone is interested.)
>
> It take a few minutes to run on a slow system and uses about 6Gbytes of disk
>
I have a little program for testing the copy_file_range(2) syscall I've been
working on. (The current version is attached, in case anyone is interested.)
It take a few minutes to run on a slow system and uses about 6Gbytes of disk
space for the file system the output file is on. (It creates 2
