From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Qu Wenruo <quwenruo@cn.fujitsu.com>,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org,
btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: About difference in extent sharing in btrfs and xfs
Date: Tue, 15 Nov 2016 00:55:26 -0800 [thread overview]
Message-ID: <20161115085526.GA18347@infradead.org> (raw)
In-Reply-To: <20161115074715.GA23680@birch.djwong.org>
On Mon, Nov 14, 2016 at 11:47:15PM -0800, Darrick J. Wong wrote:
> XFS doesn't split the extent either, internally. The FIEMAP
> implementation cross-references extent data with the refcount records,
> using extra struct fiemap_extent to report precisely which blocks are
> shared and which aren't. ocfs2 exhibits the same behavior.
And I think exact reporting of already shared extents in FIEMAP is
extremely important - independent of the internal implementation btrfs
should report the extents correctly.
prev parent reply other threads:[~2016-11-15 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 6:33 About difference in extent sharing in btrfs and xfs Qu Wenruo
2016-11-15 7:47 ` Darrick J. Wong
2016-11-15 7:53 ` Qu Wenruo
2016-11-15 8:55 ` Christoph Hellwig [this message]
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=20161115085526.GA18347@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-xfs@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).