From: Marek Otahal <markotahal@gmail.com>
To: Mark Fasheh <mfasheh@suse.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/4] [RFC] btrfs: offline dedupe
Date: Wed, 17 Apr 2013 00:50:04 +0200 [thread overview]
Message-ID: <2164102.vSxPIH87oQ@beruska> (raw)
In-Reply-To: <1366150535-18750-1-git-send-email-mfasheh@suse.de>
Hi Mark,
could you compare (appart from online/offline) your implementation to LiuBo's work?, appeared on ML a while ago:
http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg23656.html
It would be interesting if the two approaches could share some code, and also confirmation that using one technique does not
disregard using the other in future.
Best wishes,
Mark
On Tuesday 16 April 2013 15:15:31 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.
>
> 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.
>
...
>
> Code review is very much appreciated. Thanks,
> --Mark
--
Marek Otahal :o)
next prev parent reply other threads:[~2013-04-16 22:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 22:15 [PATCH 0/4] [RFC] btrfs: offline dedupe Mark Fasheh
2013-04-16 22:15 ` [PATCH 1/4] btrfs: abtract out range locking in clone ioctl() Mark Fasheh
2013-04-16 22:15 ` [PATCH 2/4] btrfs_ioctl_clone: Move clone code into it's own function Mark Fasheh
2013-04-16 22:15 ` [PATCH 3/4] btrfs: Introduce extent_read_full_page_nolock() Mark Fasheh
2013-05-06 12:38 ` David Sterba
2013-04-16 22:15 ` [PATCH 4/4] btrfs: offline dedupe Mark Fasheh
2013-05-06 12:36 ` David Sterba
2013-04-16 22:50 ` Marek Otahal [this message]
2013-04-16 23:17 ` [PATCH 0/4] [RFC] " Mark Fasheh
2013-04-17 4:00 ` Liu Bo
2013-04-20 15:49 ` Gabriel de Perthuis
2013-04-21 20:02 ` Mark Fasheh
2013-04-22 8:56 ` Gabriel de Perthuis
2013-05-07 7:33 ` [PATCH 3/4] btrfs: Introduce extent_read_full_page_nolock() Gabriel de Perthuis
2013-05-09 21:31 ` Gabriel de Perthuis
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=2164102.vSxPIH87oQ@beruska \
--to=markotahal@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mfasheh@suse.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;
as well as URLs for NNTP newsgroup(s).