linux-ext4 - Re: [PATCH bigalloc] e2fsprogs: change root-inode to extent-mapped

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] [day] [month] [year] [list]

Date:	Wed, 20 Jul 2011 13:49:37 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Andreas Dilger <aedilger@...il.com>
Cc:	"hao.bigrat@...il.com" <hao.bigrat@...il.com>,
	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
	Robin Dong <sanbai@...bao.com>
Subject: Re: [PATCH bigalloc] e2fsprogs: change root-inode to extent-mapped

On Wed, Jul 20, 2011 at 09:52:49AM -0600, Andreas Dilger wrote:
> 
> That reminds me of a question I had with bigalloc - are htree
> directories supported with bigalloc?  For a 1MB bigalloc chunksize
> it would mean a fanout of 256k, or a maximum directory size of 256GB
> with only a single level.

Yes, htree directories are supported with bigalloc; but it still works
on *blocks*, whereas *clusters* are just used for allocation purposes.

> 
> Any thoughts about increasing the directory size beyond 2GB?
> 

I think the best way to do that is to support more than two levels of
directories.  I seem to recall your telling me that one of your team
had prototyped something like this a while back?  Or is my memory
playing tricks on me?

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