On 04/28/2018 12:26 AM, Steve French wrote:
> On Sat, Apr 28, 2018 at 12:18 AM, Andreas Dilger wrote:
>> On Apr 27, 2018, at 5:41 PM, Eric Biggers wrote:
>>>
>>> On Fri, Apr 27, 2018 at 01:45:40PM -0600, Andreas Dilger wrote:
On Apr 27, 2018, at 12:25 PM, Steve French wrote:
>
> A
On Sat, Apr 28, 2018 at 12:18 AM, Andreas Dilger wrote:
> On Apr 27, 2018, at 5:41 PM, Eric Biggers wrote:
>>
>> On Fri, Apr 27, 2018 at 01:45:40PM -0600, Andreas Dilger wrote:
>>> On Apr 27, 2018, at 12:25 PM, Steve French wrote:
Are there any user space tools (other than our test too
On Apr 27, 2018, at 5:41 PM, Eric Biggers wrote:
>
> On Fri, Apr 27, 2018 at 01:45:40PM -0600, Andreas Dilger wrote:
>> On Apr 27, 2018, at 12:25 PM, Steve French wrote:
>>>
>>> Are there any user space tools (other than our test tools and xfs_io
>>> etc.) that support copy_file_range? Looks l
On Fri, Apr 27, 2018 at 01:45:40PM -0600, Andreas Dilger wrote:
> On Apr 27, 2018, at 12:25 PM, Steve French wrote:
> >
> > Are there any user space tools (other than our test tools and xfs_io
> > etc.) that support copy_file_range? Looks like at least cp and rsync
> > and dd don't. That syscal
On Apr 27, 2018, at 12:25 PM, Steve French wrote:
>
> Are there any user space tools (other than our test tools and xfs_io
> etc.) that support copy_file_range? Looks like at least cp and rsync
> and dd don't. That syscall which now has been around a couple years,
> and was reminded about at th
Are there any user space tools (other than our test tools and xfs_io
etc.) that support copy_file_range? Looks like at least cp and rsync
and dd don't. That syscall which now has been around a couple years,
and was reminded about at the LSF/MM summit a few days ago, presumably
is the 'best' way t
6 matches
Mail list logo
