linux-ext4 - Re: [RFC PATCH] ext4: Group meta-data blocks together.

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20080502181233.GA12049@skywalker>
Date:	Fri, 2 May 2008 23:42:33 +0530
From:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
To:	Andreas Dilger <adilger@....com>
Cc:	sandeen@...hat.com, linux-ext4@...r.kernel.org
Subject: Re: [RFC PATCH] ext4: Group meta-data blocks together.

On Fri, May 02, 2008 at 10:49:01AM -0700, Andreas Dilger wrote:
> On Apr 29, 2008  16:27 +0530, Aneesh Kumar K.V wrote:
> > I haven't yet tested this. Let me know what you think.
> > 
> > -aneesh
> > 
> > This adds a per inode meta-block prealloc space from which
> > meta-data block requests are served. This help in making
> > sure meta-data block are closer. This is needed to speedup
> > unlink of the file. Any new prealloc space is allocated near
> > the goal block specified. The goal block is the last block
> > allocated for the file. So we don't keep the data-block and
> > meta-data block far apart.
> 
> Does this code use the mballoc "group allocator" mechanism that it
> already uses for small files?  It would be convenient to re-use
> this code by creating a "metadata allocation group" instead of creating
> another mechanism to aggregate small IO allocations.
> 

That is mostly what it does. Except that the allocation space is hanging
from the inode rather than per-cpu.

-aneesh
--
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