From: "Pádraig Brady" <P@draigBrady.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
BTRFS MAILING LIST <linux-btrfs@vger.kernel.org>
Subject: Re: VFS support for fast copy on deduplicating FSes
Date: Thu, 25 Nov 2010 10:50:31 +0000 [thread overview]
Message-ID: <4CEE3F77.4020206@draigBrady.com> (raw)
In-Reply-To: <20101125103258.GA16562@mother.pipebreaker.pl>
On 25/11/10 10:32, Tomasz Torcz wrote:
> On Thu, Nov 25, 2010 at 04:19:17AM -0600, David Nicol wrote:
>> unresearched question/suggestion:
>>
>> Is there general support for a "fast copy" ioctl in the VFS layer,
>> which would be hooked by file systems that support COW or other form=
s
>> of deduplication and can provide copy semantics by manipulating
>> metadata only?
>>
>=20
> Yes, see reflink(2) syscall (http://lwn.net/Articles/331576/).
>=20
Yep and this: http://lwn.net/Articles/335380/
Note that cp --reflink has been supported for a while,
but it's BTRFS specific at the moment.
We'll need to change to the more generic interface.
cheers,
P=E1draig.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: "Pádraig Brady" <P@draigBrady.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
BTRFS MAILING LIST <linux-btrfs@vger.kernel.org>
Subject: Re: VFS support for fast copy on deduplicating FSes
Date: Thu, 25 Nov 2010 10:50:31 +0000 [thread overview]
Message-ID: <4CEE3F77.4020206@draigBrady.com> (raw)
In-Reply-To: <20101125103258.GA16562@mother.pipebreaker.pl>
On 25/11/10 10:32, Tomasz Torcz wrote:
> On Thu, Nov 25, 2010 at 04:19:17AM -0600, David Nicol wrote:
>> unresearched question/suggestion:
>>
>> Is there general support for a "fast copy" ioctl in the VFS layer,
>> which would be hooked by file systems that support COW or other forms
>> of deduplication and can provide copy semantics by manipulating
>> metadata only?
>>
>
> Yes, see reflink(2) syscall (http://lwn.net/Articles/331576/).
>
Yep and this: http://lwn.net/Articles/335380/
Note that cp --reflink has been supported for a while,
but it's BTRFS specific at the moment.
We'll need to change to the more generic interface.
cheers,
Pádraig.
next prev parent reply other threads:[~2010-11-25 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 10:19 VFS support for fast copy on deduplicating FSes David Nicol
2010-11-25 10:32 ` Tomasz Torcz
2010-11-25 10:50 ` Pádraig Brady [this message]
2010-11-25 10:50 ` Pádraig Brady
2010-11-25 10:36 ` Gordan Bobic
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=4CEE3F77.4020206@draigBrady.com \
--to=p@draigbrady.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.