linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Arne Jansen <sensille@gmx.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
	josef <josef@redhat.com>, miaox <miaox@cn.fujitsu.com>
Subject: Re: [PATCH] btrfs: quasi-round-robin for chunk allocation
Date: Mon, 11 Apr 2011 13:46:33 -0400	[thread overview]
Message-ID: <1302543930-sup-5927@think> (raw)
In-Reply-To: <4DA33D99.3050506@gmx.net>

Excerpts from Arne Jansen's message of 2011-04-11 13:42:49 -0400:
> On 08.02.2011 19:03, Arne Jansen wrote:
> > In a multi device setup, the chunk allocator currently always allocates
> > chunks on the devices in the same order. This leads to a very uneven
> > distribution, especially with RAID1 or RAID10 and an uneven number of
> > devices.
> > This patch always sorts the device before allocating, and allocates the
> > stripes on the devices with the most available space, as long as there
> > is enough space available. In a low space situation, it first tries to
> > maximize striping.
> > The patch also simplifies the allocator and reduces the checks for
> > corner cases. Additionally, alloc_start is now always heeded.
> 
> It's been quite some weeks since this patch has been posted. In the
> meantime several issues popped up that are already addressed by this
> patch.
> Currently multi-device btrfs just don't work as advertised, a 'balance'
> operation does not spread the data evenly over all disks and with
> multiple devices a substantial amount of space can be wasted.
> I'd be happy if someone could have a look at the patch so that chris
> can pull it. Diff did some funny things to it so it's best to just pull
> it in and read the results.

My big complaint about this patch is that it is a feature fix mixed in
with a huge cleanup.  It's hard to differentiate between the two.  Could
you please separate it out so we can review them independently?

-chris

  reply	other threads:[~2011-04-11 17:46 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
2011-03-18 19:57         ` Arne Jansen
2011-04-11 17:42 ` Arne Jansen
2011-04-11 17:46   ` Chris Mason [this message]
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=1302543930-sup-5927@think \
    --to=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).