Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
To: Chris Mason <chris.mason@oracle.com>
Cc: Marcel Lohmann <marcel@malowa.de>, linux-btrfs@vger.kernel.org
Subject: Re: Patches for BTRFS (mail-server slow down in 3.0 and more)
Date: Mon, 31 Oct 2011 16:08:32 -0200	[thread overview]
Message-ID: <orlis1xcdb.fsf@livre.localdomain> (raw)
In-Reply-To: <20111031143027.GD19328@twin.jikos.cz> (David Sterba's message of "Mon, 31 Oct 2011 15:30:27 +0100")

On Oct 31, 2011, David Sterba <dave@jikos.cz> wrote:

> On Mon, Oct 31, 2011 at 02:19:18AM -0200, Alexandre Oliva wrote:
>> On Oct 29, 2011, Chris Mason <chris.mason@oracle.com> wrote:
>> 
>> > The last one isn't a bad idea, but please do make a real mount option
>> > for it ;)
>> 
>> Like this?

> @@ -195,6 +195,7 @@ static match_table_t tokens = {
>         {Opt_subvolrootid, "subvolrootid=%d"},
>         {Opt_defrag, "autodefrag"},
>         {Opt_inode_cache, "inode_cache"},
> +       {Opt_nocluster, "nocluster"},
>         {Opt_err, NULL},

> How about 'no_alloc_cluster' ?

I considered that, too, but choosing the option name was the most
difficult part of the patch :-) I ended up going for the shorter name,
just to get the conversation started ;-) I don't feel strongly about it.

-- 
Alexandre Oliva, freedom fighter    http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/   FSF Latin America board member
Free Software Evangelist      Red Hat Brazil Compiler Engineer

      reply	other threads:[~2011-10-31 18:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4EAB270C.60406@malowa.de>
2011-10-29  4:35 ` Patches for BTRFS (mail-server slow down in 3.0 and more) Alexandre Oliva
2011-10-29  5:12   ` Chris Mason
2011-10-31  4:19     ` Alexandre Oliva
2011-10-31 14:30       ` David Sterba
2011-10-31 18:08         ` Alexandre Oliva [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=orlis1xcdb.fsf@livre.localdomain \
    --to=oliva@lsd.ic.unicamp.br \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=marcel@malowa.de \
    /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