All of lore.kernel.org
 help / color / mirror / Atom feed
From: Goffredo Baroncelli <kreijack@libero.it>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs-progs: add support for mixed data+metadata block groups V4
Date: Tue, 9 Nov 2010 19:45:50 +0100	[thread overview]
Message-ID: <201011091945.50379.kreijack@libero.it> (raw)
In-Reply-To: <1289324502-7387-1-git-send-email-mitch.harder@sabayonlinux.org>

On Tuesday, 09 November, 2010, Mitch Harder wrote:
> So alot of crazy people (I'm looking at you Meego) want to use btrfs
> on phones and such with small devices.  Unfortunately the way we split
> out metadata/data chunks it makes space usage inefficient for volumes
> that are smaller than 1gigabyte.  So add a -M option for mixing
> metadata+data, and default 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.
[...]
> @@ -274,6 +295,7 @@ static void print_usage(void)
>  	fprintf(stderr, "\t -l --leafsize size of btree leaves\n");
>  	fprintf(stderr, "\t -L --label set a label\n");
>  	fprintf(stderr, "\t -m --metadata metadata profile, values like data 
profile\n");
> +	fprintf(stderr, "\t -M --mixed mix metadata and data together\n");
>  	fprintf(stderr, "\t -n --nodesize size of btree nodes\n");
>  	fprintf(stderr, "\t -s --sectorsize min block allocation\n");
>  	fprintf(stderr, "%s\n", BTRFS_BUILD_VERSION);

Please, update the man page (mkfs.btrfs) page too with the new switch.

Regards
G.Baroncelli
-- 
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack@inwind.it>
Key fingerprint = 4769 7E51 5293 D36C 814E  C054 BF04 F161 3DC5 0512

      reply	other threads:[~2010-11-09 18:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 17:41 Btrfs-progs: add support for mixed data+metadata block groups V4 Mitch Harder
2010-11-09 18:45 ` Goffredo Baroncelli [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=201011091945.50379.kreijack@libero.it \
    --to=kreijack@libero.it \
    --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.