linux-ext4 - Re: Ext4 devel interlock meeting minutes (October 1, 2007)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <47020E59.1070609@bull.net>
Date:	Tue, 02 Oct 2007 11:24:41 +0200
From:	Valerie Clement <valerie.clement@...l.net>
To:	Avantika Mathur <mathur@...ux.vnet.ibm.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: Ext4 devel interlock meeting minutes (October 1, 2007)

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?

   Valérie

-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html