From: "Pádraig Brady" <P@draigBrady.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Thomas Meyer <thomas@m3y3r.de>, Rob Landley <rob@landley.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Copy on write hard links?
Date: Sun, 29 Sep 2013 18:19:05 +0100 [thread overview]
Message-ID: <52486109.8040806@draigBrady.com> (raw)
In-Reply-To: <CAFLxGvzCp1JDL5yfuk7oRBGqi+re=NZWr-mg6nahs9NjFyDYwA@mail.gmail.com>
On 09/29/2013 08:14 AM, Richard Weinberger wrote:
> On Sun, Sep 29, 2013 at 7:22 AM, Pádraig Brady <P@draigbrady.com> wrote:
>> On 09/25/2013 03:37 PM, richard -rw- weinberger wrote:
>>> On Wed, Sep 25, 2013 at 4:28 PM, Thomas Meyer <thomas@m3y3r.de> wrote:
>>>> Am Mittwoch, den 25.09.2013, 08:59 -0500 schrieb Rob Landley:
>>>>> On 09/24/2013 01:36:56 PM, Thomas Meyer wrote:
>>>>>> Hi,
>>>>>>
>>>>>> Is there such a thing?
>>>>>
>>>>> In the kernel's vfs layer?
>>>>
>>>> Yes, that would be a nice feature!
>>>
>>> You mean reflinks?
>>> Currently only OCFS2 and btrfs support them.
>>> Both using a fs specific ioctl().
>>> IIRC GNU cp uses the btrfs specific one if the --reflink parameter is used.
>>
>> coreutils is waiting for a reflink syscall to materialize
>> rather than adding new per filesystem support
>> http://lwn.net/Articles/335380/
>
> Is this the correct link? It's a proposal for a reflink() syscall.
> But corrently both OCFS2 and btrfs are using ioctl().
>
> Digging into GNU coreutils shows that their cp's
> clone_file() only supports the btrfs ioctl().
> I don't know what the GNU folks big plan is, maybe you know more. :-)
The current coreutils plan is to not to call any more file system specific ioctls,
rather waiting until a more general syscall is available.
thanks,
Pádraig.
next prev parent reply other threads:[~2013-09-29 17:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 18:36 Copy on write hard links? Thomas Meyer
2013-09-25 1:40 ` Adam Borowski
2013-09-25 13:59 ` Rob Landley
2013-09-25 14:28 ` Thomas Meyer
2013-09-25 14:37 ` richard -rw- weinberger
2013-09-29 5:22 ` Pádraig Brady
2013-09-29 7:14 ` Richard Weinberger
2013-09-29 17:19 ` Pádraig Brady [this message]
2013-12-13 22:58 ` Jörn Engel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52486109.8040806@draigBrady.com \
--to=p@draigbrady.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
--cc=rob@landley.net \
--cc=thomas@m3y3r.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox