From: cwillu <cwillu@cwillu.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: Arne Jansen <sensille@gmx.net>, miaox <miaox@cn.fujitsu.com>,
josef <josef@redhat.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: quasi-round-robin for chunk allocation
Date: Fri, 18 Mar 2011 10:25:49 -0600 [thread overview]
Message-ID: <AANLkTimx2BrXuSpKzcjV3EC3MO0YFAWFszg5hJDhKjgJ@mail.gmail.com> (raw)
In-Reply-To: <1300458780-sup-7019@think>
On Fri, Mar 18, 2011 at 8:40 AM, Chris Mason <chris.mason@oracle.com> w=
rote:
> I think that filling all the devices fully is more important than the
> initial spread. =A0Miao is correct that the administrator will
> probably complain if all the devices aren't used for the initial stri=
pes.
> But, over the long term the admin does expect that if he gives us 350=
GB
> of drives in any config, we find try our best to use all 350GB. =A0I'=
d
> rather meet that expectation than worry about initial performance in =
a
> mixed drive setup.
There's no reason why you can't get optimal distribution from the
start while still having complete usage. And it's preferable to do
that, so that you get optimal distribution even as you add capacity;
otherwise front-loading the worst cases makes sure you run into them,
even if the administrator would have added more disks before you
needed to handle them.
--
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:[~2011-03-18 16:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 18:03 [PATCH] btrfs: quasi-round-robin for chunk allocation Arne Jansen
2011-02-09 3:03 ` Miao Xie
2011-03-17 15:58 ` Arne Jansen
2011-03-18 14:40 ` Chris Mason
2011-03-18 16:25 ` cwillu [this message]
2011-03-18 19:57 ` Arne Jansen
2011-04-11 17:42 ` Arne Jansen
2011-04-11 17:46 ` Chris Mason
2011-05-13 12:56 ` David Sterba
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=AANLkTimx2BrXuSpKzcjV3EC3MO0YFAWFszg5hJDhKjgJ@mail.gmail.com \
--to=cwillu@cwillu.com \
--cc=chris.mason@oracle.com \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaox@cn.fujitsu.com \
--cc=sensille@gmx.net \
/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).