linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Fasheh <mfasheh@suse.de>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.cz>
Subject: Re: [PATCH v13 00/15] Btrfs In-band De-duplication
Date: Fri, 9 Sep 2016 17:22:59 -0700	[thread overview]
Message-ID: <20160910002259.GR5316@wotan.suse.de> (raw)
In-Reply-To: <20160908071304.25616-1-quwenruo@cn.fujitsu.com>

On Thu, Sep 08, 2016 at 03:12:49PM +0800, Qu Wenruo wrote:
> This patchset can be fetched from github:
> https://github.com/adam900710/linux.git wang_dedupe_20160907
> 
> This version is just another small update, rebased to David's
> for-next-20160906 branch.
> 
> This updates only includes one small fix, which is exposed by recent
> commits which checks space_info->bytes_may_use at umount time.
> Caused by that we only free quota reserved space at hash hit, but doesn't
> free space_info->bytes_may_use.
> 
> Other rebase changes are all related to recent infrastructure change,
> like io_tree and quota flags change.
> 
> We ran xfstests with dedupe enabled.

Is there an xfstests patch for this I can look at? We want to be able to run
and reproduce the same tests as you.

Also where are the disk portion patches or did I miss them somehow?
	--Mark

--
Mark Fasheh

  parent reply	other threads:[~2016-09-10  0:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08  7:12 [PATCH v13 00/15] Btrfs In-band De-duplication Qu Wenruo
2016-09-08  7:12 ` [PATCH v13 01/15] btrfs: expand btrfs_set_extent_delalloc() and its friends to support in-band dedupe and subpage size patchset Qu Wenruo
2016-09-08  7:12 ` [PATCH v13 02/15] btrfs: dedupe: Introduce dedupe framework and its header Qu Wenruo
2016-09-08  7:12 ` [PATCH v13 03/15] btrfs: dedupe: Introduce function to initialize dedupe info Qu Wenruo
2016-09-08  7:12 ` [PATCH v13 04/15] btrfs: dedupe: Introduce function to add hash into in-memory tree Qu Wenruo
2016-09-08  7:12 ` [PATCH v13 05/15] btrfs: dedupe: Introduce function to remove hash from " Qu Wenruo
2016-09-08  7:12 ` [PATCH v13 06/15] btrfs: delayed-ref: Add support for increasing data ref under spinlock Qu Wenruo
2016-09-08  7:12 ` [PATCH v13 07/15] btrfs: dedupe: Introduce function to search for an existing hash Qu Wenruo
2016-09-08  7:12 ` [PATCH v13 08/15] btrfs: dedupe: Implement btrfs_dedupe_calc_hash interface Qu Wenruo
2016-09-08  7:12 ` [PATCH v13 09/15] btrfs: ordered-extent: Add support for dedupe Qu Wenruo
2016-09-08  7:12 ` [PATCH v13 10/15] btrfs: dedupe: Inband in-memory only de-duplication implement Qu Wenruo
2016-09-08  7:13 ` [PATCH v13 11/15] btrfs: dedupe: Add ioctl for inband dedupelication Qu Wenruo
2016-09-08  7:13 ` [PATCH v13 12/15] btrfs: relocation: Enhance error handling to avoid BUG_ON Qu Wenruo
2016-09-08  7:13 ` [PATCH v13 13/15] btrfs: improve inode's outstanding_extents computation Qu Wenruo
2016-09-08  7:13 ` [PATCH v13 14/15] btrfs: dedupe: fix false ENOSPC Qu Wenruo
2016-09-08  7:13 ` [PATCH v13 15/15] btrfs: dedupe: Introduce new reconfigure ioctl Qu Wenruo
2016-09-09 15:20 ` [PATCH v13 00/15] Btrfs In-band De-duplication David Sterba
2016-09-10  0:22 ` Mark Fasheh [this message]
2016-09-10  7:58   ` Qu Wenruo
2016-10-17 14:30 ` David Sterba
2016-10-19  6:20   ` 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=20160910002259.GR5316@wotan.suse.de \
    --to=mfasheh@suse.de \
    --cc=dsterba@suse.cz \
    --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).