From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Valerie Clement <valerie.clement@bull.net>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: start seraching for the right extent from the goal group.
Date: Thu, 1 May 2008 21:18:24 +0530 [thread overview]
Message-ID: <20080501154824.GB7005@skywalker> (raw)
In-Reply-To: <48187EEF.8000101@bull.net>
On Wed, Apr 30, 2008 at 04:15:11PM +0200, Valerie Clement wrote:
> Aneesh Kumar K.V wrote:
>> With mballoc we search for the best extent using different
>> criteria. We should always use the goal group when we are
>> starting with a new criteria.
>
> Hi Aneesh,
>
> as you are working on the mballoc code, there is another thing
> which is not clear for me: why skipping uninitialized groups in
> ext4_mb_good_group() when criteria is 0.
> I'm doing tests on large partition (~2TB) and on FS with 1KB
> block size and it impacts the performance when the number of
> groups is great (and the uninit_groups feature is used of course).
> For which reason we skip these groups ?
>
The reason is to avoid initializing block group. We would like to make
sure when we are allocating blocks we allocate them from already
initialized group. Otherwise we would end up initializing multiple block
group with in turn decrease the performance advantage of uninit_group.
The current logic is.
If request len is order of 2 we start with cr=0.
If we are cr=0 skip the uninit block group and search for the right
count of blocks in other initialized block group using simple_scan
logic.
If we don't find the right count of blocks then cr++;
if cr != 0 don't skip uninit block group.
if group is uninit and the request size is order of 2 use the
simple_scan logic which use buddy cache to search for the right count of
block group.
That way we avoid allocating blocks out of uninit group in the first
loop. We allocate blocks only after we looked at all the other
initialized block group.
-aneesh
prev parent reply other threads:[~2008-05-01 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 11:16 [PATCH] ext4: start seraching for the right extent from the goal group Aneesh Kumar K.V
2008-04-30 12:58 ` Eric Sandeen
2008-05-01 15:37 ` Aneesh Kumar K.V
2008-05-02 18:53 ` Andreas Dilger
2008-05-02 21:11 ` Mingming Cao
[not found] ` <48187EEF.8000101@bull.net>
2008-05-01 15:48 ` Aneesh Kumar K.V [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=20080501154824.GB7005@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