From: Jitendra <jkhasdev@gmail.com>
To: quwenruo@cn.fujitsu.com
Cc: linux-btrfs@vger.kernel.org
Subject: How to test in-bound dedupe
Date: Tue, 28 Mar 2017 23:22:15 +0530 [thread overview]
Message-ID: <20170328175215.GA14991@jitendra-HP-ProBook> (raw)
Hi Qu/All,
I am looking into in-memory in-bound dedup. I have cloned your git tree from
following urls.
Linux Tree: https://github.com/adam900710/linux.git wang_dedupe_latest
btrfs-progs: https://git@github.com:adam900710/btrfs-progs.git dedupe_20170316
Then run the follwoing test https://btrfs.wiki.kernel.org/index.php/User_notes_on_dedupe.
Is there any stuff that needs to be tested for it? if something, then please
point out me.
My goal is to understand in-memory dedup and try to participate in on-disk
de-dup.
---
Jitendra
next reply other threads:[~2017-03-28 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 17:52 Jitendra [this message]
2017-03-29 0:55 ` How to test in-bound dedupe Qu Wenruo
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=20170328175215.GA14991@jitendra-HP-ProBook \
--to=jkhasdev@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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 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).