linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [RFC PATCH v3 0/2] Online data deduplication
Date: Thu,  2 May 2013 00:27:36 +0800	[thread overview]
Message-ID: <1367425659-10803-1-git-send-email-bo.li.liu@oracle.com> (raw)

NOTE: This leads to a FORMAT CHANGE, DO NOT use it on real data!

Data deduplication is a specialized data compression technique for eliminating
duplicate copies of repeating data.[1]

This patch set is also related to "Content based storage" in project ideas[2].

PATCH 1 is a hang fix when deduplication is on, but it's also useful with no
deduplication in practice use.

For more implementation details, please refer to PATCH 2.

TODO:
* a bit-to-bit comparison callback.

All comments are welcome!

[1]: http://en.wikipedia.org/wiki/Data_deduplication
[2]: https://btrfs.wiki.kernel.org/index.php/Project_ideas#Content_based_storage


v3:
  * add COMPRESS support
  * add a real ioctl to enable dedup feature
  * change the maximum allowed dedup blocksize to 128k because of compressed
    range limit
v2:
  * To avoid enlarging the file extent item's size, add another index key used
    for freeing dedup extent.
  * Freeing dedup extent is now like how we delete checksum.
  * Add support for alternative deduplicatin blocksize larger than PAGESIZE.
  * Add a mount option to set deduplication blocksize.
  * Add support for those writes that are smaller than deduplication blocksize.

=====================
HOW To turn deduplication on:

There are 2 steps you need to do before using it,
1) mount /dev/disk /mnt_of_your_btrfs -o dedup
   (or mount /dev/disk /mnt_of_your_btrfs -o dedup_bs=128K)
2) btrfs filesystem dedup-register /mnt_of_your_btrfs
=====================

Liu Bo (2):
  Btrfs: skip merge part for delayed data refs
  Btrfs: online data deduplication

 fs/btrfs/ctree.h           |   54 ++++
 fs/btrfs/delayed-ref.c     |    7 +
 fs/btrfs/disk-io.c         |   34 +++-
 fs/btrfs/extent-tree.c     |    7 +
 fs/btrfs/extent_io.c       |   27 ++-
 fs/btrfs/extent_io.h       |   15 ++
 fs/btrfs/file-item.c       |  242 ++++++++++++++++++
 fs/btrfs/inode.c           |  583 ++++++++++++++++++++++++++++++++++++++------
 fs/btrfs/ioctl.c           |   38 +++
 fs/btrfs/ordered-data.c    |   30 ++-
 fs/btrfs/ordered-data.h    |   11 +-
 fs/btrfs/super.c           |   27 ++-
 include/uapi/linux/btrfs.h |    1 +
 13 files changed, 990 insertions(+), 86 deletions(-)

-- 
1.7.7


             reply	other threads:[~2013-05-01 16:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 16:27 Liu Bo [this message]
2013-05-01 16:27 ` [PATCH v3 1/2] Btrfs: skip merge part for delayed data refs Liu Bo
2013-05-01 16:27 ` [PATCH v3 2/2] Btrfs: online data deduplication Liu Bo
2013-05-01 17:30   ` Josef Bacik
2013-05-01 18:07   ` Gabriel de Perthuis
2013-05-01 16:27 ` [PATCH] Btrfs-progs: add dedup register Liu Bo
2013-05-13 15:55   ` David Sterba
2013-05-14  0:29     ` Liu Bo
2013-05-01 17:37 ` [RFC PATCH v3 0/2] Online data deduplication Josef Bacik
2013-05-03  7:54   ` Liu Bo

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=1367425659-10803-1-git-send-email-bo.li.liu@oracle.com \
    --to=bo.li.liu@oracle.com \
    --cc=linux-btrfs@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 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).