From: Josef Bacik <josef@redhat.com>
To: "Cláudio Martins" <ctpm@ist.utl.pt>
Cc: Josef Bacik <josef@redhat.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs-progs: add support for mixed data+metadata block groups V3
Date: Thu, 28 Oct 2010 21:03:08 -0400 [thread overview]
Message-ID: <20101029010308.GC11684@dhcp231-156.rdu.redhat.com> (raw)
In-Reply-To: <20101029012013.68a18b8a.ctpm@ist.utl.pt>
On Fri, Oct 29, 2010 at 01:20:13AM +0100, Cl=E1udio Martins wrote:
>=20
> On Wed, 27 Oct 2010 14:37:34 -0400 Josef Bacik <josef@redhat.com> wro=
te:
> > So alot of crazy people (I'm looking at you Meego) want to use btrf=
s on phones
> > and such with small devices. Unfortunately the way we split out me=
tadata/data
> > chunks it makes space usage inefficient for volumes that are smalle=
r than
> > 1gigabyte. So add a -M option for mixing metadata+data, and defaul=
t to this
> > mixed mode if the filesystem is less than or equal to 1 gigabyte. =
I've tested
> > this with xfstests on a 100mb filesystem and everything is a-ok.
> >=20
>=20
> Hi,
>=20
> Could you provide some rationale as to why btrfs should support thes=
e
> two modes of data/metadata (mixed and separate) allocation instead of
> just always doing mixed data+metadata?
>
It makes the volume management stuff easier and gives us more flexibili=
ty for
how we lay out data and metadata. Thanks,
Josef=20
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-10-29 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 18:37 [PATCH] Btrfs-progs: add support for mixed data+metadata block groups V3 Josef Bacik
2010-10-29 0:20 ` Cláudio Martins
2010-10-29 1:03 ` Josef Bacik [this message]
2010-11-06 21:10 ` Mitch Harder
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=20101029010308.GC11684@dhcp231-156.rdu.redhat.com \
--to=josef@redhat.com \
--cc=ctpm@ist.utl.pt \
--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 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).