From: Eryu Guan <eguan@redhat.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Btrfs in-band de-duplication test cases
Date: Tue, 21 Mar 2017 14:05:33 +0800 [thread overview]
Message-ID: <20170321060533.GS14226@eguan.usersys.redhat.com> (raw)
In-Reply-To: <5a01bd29-d691-24e0-8c8f-3c5dc30370ca@cn.fujitsu.com>
On Tue, Mar 21, 2017 at 01:22:33PM +0800, Qu Wenruo wrote:
>
>
> At 03/21/2017 12:51 PM, Eryu Guan wrote:
> > Hi Qu,
> >
> > On Thu, Mar 16, 2017 at 05:08:48PM +0800, Qu Wenruo wrote:
> > > Btrfs in-band de-duplication test cases for in-memory backend, which covers
> > > the bugs exposed during the development.
> >
> > Do you have a kernel tree that contains the in-band patches so that I
> > and others could try and run these tests?
>
> Of course.
>
> Kernel tree:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_adam900710_linux.git&d=DwIBAg&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=-yMrTV4jriXR7ieyzzjV-QgHBD0UDw8ixoR77aMeAHE&m=YzsA7J_jQbbCdcg4s_RD-fVgAB-E0z9HI7TsNs0ISJ8&s=3WywXrgANPtqSESgw9Ey4wt8D3niq7n9yhn2W_lat1c&e= wang_dedupe_latest
>
> Btrfs-progs tree:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_adam900710_btrfs-2Dprogs.git&d=DwIBAg&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=-yMrTV4jriXR7ieyzzjV-QgHBD0UDw8ixoR77aMeAHE&m=YzsA7J_jQbbCdcg4s_RD-fVgAB-E0z9HI7TsNs0ISJ8&s=8wuw_b8hI8oTVNrb2E_N0mqv8jzV8svYD6gcotli0eY&e= dedupe_20170306
Thanks! But I guess it's branch 'dedupe_20170316' of btrfs-progs repo,
right? There's no dedupe_20170306 branch.
Thanks,
Eryu
--
To unsubscribe from this list: send the line "unsubscribe fstests" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at https://urldefense.proofpoint.com/v2/url?u=http-3A__vger.kernel.org_majordomo-2Dinfo.html&d=DwIBAg&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=-yMrTV4jriXR7ieyzzjV-QgHBD0UDw8ixoR77aMeAHE&m=YzsA7J_jQbbCdcg4s_RD-fVgAB-E0z9HI7TsNs0ISJ8&s=r92jDqcAqEQ6yzfk0gRIezOrZmWu-Nm5X5Rdo7mS0rM&e=
next prev parent reply other threads:[~2017-03-21 6:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 9:08 [PATCH v2 0/3] Btrfs in-band de-duplication test cases Qu Wenruo
2017-03-16 9:08 ` [PATCH v2 1/3] fstests: btrfs: Add basic test for btrfs in-band de-duplication Qu Wenruo
2017-03-16 9:08 ` [PATCH v2 2/3] fstests: btrfs: Add testcase for btrfs dedupe and metadata balance race test Qu Wenruo
2017-03-16 9:08 ` [PATCH v2 3/3] fstests: btrfs: Test inband dedupe with data balance Qu Wenruo
2017-03-21 8:44 ` Eryu Guan
2017-03-21 4:51 ` [PATCH v2 0/3] Btrfs in-band de-duplication test cases Eryu Guan
2017-03-21 5:22 ` Qu Wenruo
2017-03-21 6:05 ` Eryu Guan [this message]
2017-03-21 7:07 ` 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=20170321060533.GS14226@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--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