From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Valerie Clement <valerie.clement@bull.net>
Cc: Avantika Mathur <mathur@linux.vnet.ibm.com>, linux-ext4@vger.kernel.org
Subject: Re: Ext4 devel interlock meeting minutes (October 1, 2007)
Date: Tue, 02 Oct 2007 17:06:48 +0530 [thread overview]
Message-ID: <47022D50.2040908@linux.vnet.ibm.com> (raw)
In-Reply-To: <47020E59.1070609@bull.net>
Valerie Clement wrote:
> Avantika Mathur wrote:
>> Multiple Block Allocation:
>> - Main outstanding issue is still need for better documentation of the
>> code.
>> - Aneesh has marked the places that need explanation with fixme, and
>> Alex will be adding the needed comments. If this gets done quickly,
>> we can try to push this feature to 2.6.24
>> - Aneesh has asked for recommendations for a benchmark to run which
>> will test the mballoc allocator. Mingming suggested using dd and
>> dbench, as was done in the past for basic mballoc patches. To test
>> the in-core preallocation, kernel untar tests. Look at the file
>> fragmentation after running the test.
>
> Currently, the mballoc feature is not compatible with the uninit_groups
> feature. I have just tried a simple test which failed. Isn't this a
> problem?
>
> Another point that is not clear for me, is mballoc compatible with
> delalloc now, or is there still a restriction?
>
I thought i had merged the patch from Andreas.
http://marc.info/?l=linux-ext4&m=118833298930860&w=2
But i don't see it in mballoc-core.patch
Will update the mballoc patch
-aneesh
next prev parent reply other threads:[~2007-10-02 11:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 22:10 Ext4 devel interlock meeting minutes (October 1, 2007) Avantika Mathur
2007-10-02 5:58 ` Andreas Dilger
2007-10-02 14:23 ` Eric Sandeen
2007-10-02 9:24 ` Valerie Clement
2007-10-02 11:36 ` Aneesh Kumar K.V [this message]
2007-10-02 14:12 ` Andreas Dilger
2007-10-02 18:10 ` 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=47022D50.2040908@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mathur@linux.vnet.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).