public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Valerie Clement <valerie.clement@bull.net>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: Problems with mballoc and uninit_groups option
Date: Fri, 11 Jan 2008 21:15:52 +0530	[thread overview]
Message-ID: <20080111154552.GA7339@skywalker> (raw)
In-Reply-To: <47877758.1070603@bull.net>

On Fri, Jan 11, 2008 at 03:04:08PM +0100, Valerie Clement wrote:
> Hi,
>
> I've got problems with mballoc when I create the ext4 filesystem with  
> the "uninit_groups" option enabled.
>
> First, I do a single test on a filesystem created without the  
> "uninit_groups" option and mounted with the defaults option:
>   dd if=/dev/zero of=/mnt/test/foo bs=1M count=1024
>
> In this case, the file blocks are allocated in the groups 4, 5, 6, 7, 8,  
> 9, 10.
>
> When the filesystem is created with the "uninit_groups" option enabled  
> and mounted with the defaults option, I do the same dd command.
>
> In this case, the file blocks are allocated in the groups 5, 7, 9, 25,  
> 27, 49, 81. It seems that the blocks could be allocated only in the  
> already initialized groups.
>

That is because we skip the uninitialized group in ext4_mb_good_group.
I guess we are trying criteria 0 allocation and we skip uninit group for
criteria 0 . You can tune by setting higher value for
/proc/fs/ext4/partition/orders2_req. Setting it to a high value would
skip criteria 0 allocation for small requests.

I guess you are using delayed allocation ?

-aneesh

  reply	other threads:[~2008-01-11 15:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-11 14:04 Problems with mballoc and uninit_groups option Valerie Clement
2008-01-11 15:45 ` Aneesh Kumar K.V [this message]
2008-01-14 14:05   ` Valerie Clement

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=20080111154552.GA7339@skywalker \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=valerie.clement@bull.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