From: Josef Bacik <jbacik@fusionio.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Josef Bacik <jbacik@fusionio.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: incompatible format change to remove hole extents V2
Date: Tue, 29 Oct 2013 14:30:13 -0400 [thread overview]
Message-ID: <20131029183013.GH4543@localhost.localdomain> (raw)
In-Reply-To: <526FFB38.4030008@suse.com>
On Tue, Oct 29, 2013 at 02:15:20PM -0400, Jeff Mahoney wrote:
> On 10/29/13, 9:56 AM, Josef Bacik wrote:
> > Btrfs has always had these filler extent data items for holes in inodes. This
> > has made somethings very easy, like logging hole punches and sending hole
> > punches. However for large holey files these extent data items are pure
> > overhead. So add an incompatible feature to no longer add hole extents to
> > reduce the amount of metadata used by these sort of files. This has a few
> > changes for logging and send obviously since they will need to detect holes and
> > log/send the holes if there are any. I've tested this thoroughly with xfstests
> > and it doesn't cause any issues with and without the incompat format set.
> > Thanks,
>
> This sounds like it could be a candidate for the online-enable mask in
> my feature ioctl patchset.
Yeah once I pull your stuff in I'll add it. Thanks,
Josef
prev parent reply other threads:[~2013-10-29 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 13:56 [PATCH] Btrfs: incompatible format change to remove hole extents V2 Josef Bacik
2013-10-29 18:15 ` Jeff Mahoney
2013-10-29 18:30 ` Josef Bacik [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=20131029183013.GH4543@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=jeffm@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.