From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: adilger@sun.com, linux-ext4@vger.kernel.org, cmm@us.ibm.com,
tytso@mit.edu
Subject: Re: [PATCH] ext4: start seraching for the right extent from the goal group.
Date: Thu, 1 May 2008 21:07:47 +0530 [thread overview]
Message-ID: <20080501153747.GA7005@skywalker> (raw)
In-Reply-To: <48186CFB.8050206@redhat.com>
On Wed, Apr 30, 2008 at 07:58:35AM -0500, Eric Sandeen 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.
>
> Aneesh, is there any testcase etc that will demonstrate the resulting
> difference in layout?
>
> It's not clear to me from this changelog (without looking at a lot more
> context) exactly what you're changing and why...
I don't have any specific test case. With mballoc depending on the
request size we follow different criteria to allocate blocks. For
example if the size is stripe size multiple we use criteria 1 and start
searching for the right blocks from block group starting with goal
group. If we don't find right count of blocks, we use criteria 2 and start
searching from the group block 0. I guess with criteria 2 also, we should start
searching from the goal group so that when we find the right count of
blocks we find them close to the goal group.
-aneesh
next prev parent reply other threads:[~2008-05-01 15:38 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 [this message]
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
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=20080501153747.GA7005@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=adilger@sun.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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