From: Ric Wheeler <ricwheeler@gmail.com>
To: Mark Fasheh <mfasheh@suse.de>
Cc: linux-btrfs@vger.kernel.org, Josef Bacik <josef@redhat.com>,
Chris Mason <chris.mason@fusionio.com>,
Gabriel de Perthuis <g2p.code@gmail.com>,
David Sterba <dsterba@suse.cz>, Zach Brown <zab@redhat.com>
Subject: Re: [PATCH 0/4] btrfs: offline dedupe v3
Date: Fri, 26 Jul 2013 12:48:19 -0400 [thread overview]
Message-ID: <51F2A853.3000006@gmail.com> (raw)
In-Reply-To: <1374856212-11228-1-git-send-email-mfasheh@suse.de>
On 07/26/2013 12:30 PM, Mark Fasheh wrote:
> Hi,
>
> The following series of patches implements in btrfs an ioctl to do
> offline deduplication of file extents.
>
> To be clear, "offline" in this sense means that the file system is
> mounted and running, but the dedupe is not done during file writes,
> but after the fact when some userspace software initiates a dedupe.
I think that you might want to use the terms "inband" and "out of band" which
seem to be used in the "de dup" storage space a bit more often. Offline
definitely carries the wrong connotation :)
ric
>
> The primary patch is loosely based off of one sent by Josef Bacik back
> in January, 2011.
>
> http://permalink.gmane.org/gmane.comp.file-systems.btrfs/8508
>
> I've made significant updates and changes from the original. In
> particular the structure passed is more fleshed out, this series has a
> high degree of code sharing between itself and the clone code, and the
> locking has been updated.
prev parent reply other threads:[~2013-07-26 16:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 16:30 [PATCH 0/4] btrfs: offline dedupe v3 Mark Fasheh
2013-07-26 16:30 ` [PATCH 1/4] btrfs: abtract out range locking in clone ioctl() Mark Fasheh
2013-07-26 16:30 ` [PATCH 2/4] btrfs_ioctl_clone: Move clone code into it's own function Mark Fasheh
2013-07-26 16:30 ` [PATCH 3/4] btrfs: Introduce extent_read_full_page_nolock() Mark Fasheh
2013-07-26 16:30 ` [PATCH 4/4] btrfs: offline dedupe Mark Fasheh
2013-07-26 22:09 ` Zach Brown
2013-07-26 16:48 ` Ric Wheeler [this message]
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=51F2A853.3000006@gmail.com \
--to=ricwheeler@gmail.com \
--cc=chris.mason@fusionio.com \
--cc=dsterba@suse.cz \
--cc=g2p.code@gmail.com \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mfasheh@suse.de \
--cc=zab@redhat.com \
/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.