From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org,
Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>,
Chandan Rajendra <chandan@linux.vnet.ibm.com>
Subject: Re: [PATCH v12.1 01/15] btrfs: expand cow_file_range() to support in-band dedup and subpage-blocksize
Date: Mon, 11 Jul 2016 18:41:29 +0200 [thread overview]
Message-ID: <20160711164129.GA13336@suse.cz> (raw)
In-Reply-To: <20160711030543.30115-2-quwenruo@cn.fujitsu.com>
On Mon, Jul 11, 2016 at 11:05:29AM +0800, Qu Wenruo wrote:
> From: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
>
> Extract cow_file_range() new parameters for both in-band dedupe and
> subpage sector size patchset.
>
> This should make conflict of both patchset to minimal, and reduce the
> effort needed to rebase them.
Great, thanks. I did a test merge, there are still conflicts but they
seem to be resolvable more easily, picking the changes from the right
patchset. I haven't tested it so there's more work, but the point was to
get the conflict surface down.
There's another candidate, btrfs_set_extent_delalloc as it adds a
parameter, can you please send a similar patch for that?
next prev parent reply other threads:[~2016-07-11 16:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 3:05 [PATCH v12.1 00/15] Btrfs in-band de-duplication Qu Wenruo
2016-07-11 3:05 ` [PATCH v12.1 01/15] btrfs: expand cow_file_range() to support in-band dedup and subpage-blocksize Qu Wenruo
2016-07-11 16:41 ` David Sterba [this message]
2016-07-12 4:50 ` Satoru Takeuchi
2016-07-19 6:40 ` Qu Wenruo
2016-07-11 3:05 ` [PATCH v12.1 02/15] btrfs: dedupe: Introduce dedupe framework and its header Qu Wenruo
2016-07-11 3:05 ` [PATCH v12.1 03/15] btrfs: dedupe: Introduce function to initialize dedupe info Qu Wenruo
2016-07-11 3:05 ` [PATCH v12.1 04/15] btrfs: dedupe: Introduce function to add hash into in-memory tree Qu Wenruo
2016-07-11 3:05 ` [PATCH v12.1 05/15] btrfs: dedupe: Introduce function to remove hash from " Qu Wenruo
2016-07-11 3:05 ` [PATCH v12.1 06/15] btrfs: delayed-ref: Add support for increasing data ref under spinlock Qu Wenruo
2016-07-11 3:05 ` [PATCH v12.1 07/15] btrfs: dedupe: Introduce function to search for an existing hash Qu Wenruo
2016-07-11 3:05 ` [PATCH v12.1 08/15] btrfs: dedupe: Implement btrfs_dedupe_calc_hash interface Qu Wenruo
2016-07-11 3:05 ` [PATCH v12.1 09/15] btrfs: ordered-extent: Add support for dedupe Qu Wenruo
2016-07-11 3:05 ` [PATCH v12.1 10/15] btrfs: dedupe: Inband in-memory only de-duplication implement Qu Wenruo
2016-07-11 3:05 ` [PATCH v12.1 11/15] btrfs: dedupe: Add ioctl for inband dedupelication Qu Wenruo
2016-07-11 3:05 ` [PATCH v12.1 12/15] btrfs: relocation: Enhance error handling to avoid BUG_ON Qu Wenruo
2016-07-11 3:05 ` [PATCH v12.1 13/15] btrfs: improve inode's outstanding_extents computation Qu Wenruo
2016-07-11 3:05 ` [PATCH v12.1 14/15] btrfs: dedupe: fix false ENOSPC Qu Wenruo
2016-07-11 3:05 ` [PATCH v12.1 15/15] btrfs: dedupe: Introduce new reconfigure ioctl Qu Wenruo
2016-07-11 3:08 ` [PATCH v12.1 00/15] Btrfs in-band de-duplication 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=20160711164129.GA13336@suse.cz \
--to=dsterba@suse.cz \
--cc=chandan@linux.vnet.ibm.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.com \
--cc=wangxg.fnst@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).