From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Al <6401e46d@opayq.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls.
Date: Tue, 2 Feb 2016 10:55:01 +0800 [thread overview]
Message-ID: <56B01A85.80507@cn.fujitsu.com> (raw)
In-Reply-To: <loom.20160122T122307-195@post.gmane.org>
You're right, I misunderstood the mail and get a little emotional.
And sorry for that inappropriate reply.
BTW, the new patchset will be sent to btrfs mail list in coming hour, if
you're interested in inband de-dup, you can try the following github
repos to build and test in-band de-dup:
Kernel
https://github.com/adam900710/linux.git wang_dedup
Btrfs-progs
https://github.com/adam900710/btrfs-progs.git dedup
And if you have any concern on the implementation or the dedup related
Document, I'm happy to hear.
(I was a little emotional just because some unexpected bugs that time.)
Thanks,
Qu
Al wrote on 2016/01/22 11:33 +0000:
> With respect Chris, if you intentionally ignore all of the other context
> clues ("keep up the great work", "looking forward to using it"), you could
> come to that conclusion. You'd have to try really really hard.
>
> I wasn't criticising your buddy in anyway, quite the opposite. Can we move
> on, now? There are better ways of spending our time.
>
>
>
>
>
>
> --
> 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
>
>
next prev parent reply other threads:[~2016-02-02 2:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-16 12:27 Why is dedup inline, not delayed (as opposed to offline)? Explain like I'm five pls Al
2016-01-16 14:10 ` Duncan
2016-01-16 18:07 ` Rich Freeman
2016-01-18 12:23 ` Austin S. Hemmelgarn
2016-01-23 22:22 ` Mark Fasheh
2016-01-20 14:49 ` Al
2016-01-20 14:43 ` Al
2016-01-21 8:23 ` Qu Wenruo
2016-01-21 14:53 ` Al
2016-01-21 17:23 ` Chris Murphy
2016-01-22 11:33 ` Al
2016-01-23 2:44 ` Chris Murphy
2016-02-02 2:55 ` Qu Wenruo [this message]
2016-01-18 1:36 ` Qu Wenruo
2016-01-18 3:10 ` Duncan
2016-01-18 3:16 ` Qu Wenruo
2016-01-18 3:51 ` Duncan
2016-01-18 12:48 ` Austin S. Hemmelgarn
2016-01-19 8:30 ` Duncan
2016-01-19 9:14 ` Duncan
2016-01-19 12:28 ` Austin S. Hemmelgarn
2016-01-19 15:40 ` Duncan
2016-01-20 8:32 ` Brendan Hide
2016-01-19 12:21 ` Austin S. Hemmelgarn
2016-01-20 15:12 ` Al
2016-01-20 18:21 ` Duncan
2016-01-20 14:53 ` Al
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=56B01A85.80507@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=6401e46d@opayq.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).