linux-ext4 - Re: An idea for supporting large directories and readdir+stat workloads

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]

Message-ID: <20120813143941.GC32484@thunk.org>
Date:	Mon, 13 Aug 2012 10:39:41 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Andreas Dilger <aedilger@...il.com>
Cc:	Jeff Moyer <jmoyer@...hat.com>,
	Ext4 Developers List <linux-ext4@...r.kernel.org>
Subject: Re: An idea for supporting large directories and readdir+stat
 workloads

On Mon, Aug 13, 2012 at 10:36:07AM -0400, Theodore Ts'o wrote:
> Field		Size
> 
> ino		 4

Silly me, we don't need actually need to store the inode a second
time, since that's already in the struct ext4_dir_entry.

> dev		 4

... and we only need to store the device if this is a block or
character device, so we could actually use the i_size field below to
store the dev_t for devices inodes.

So this would shrink the size of the "compact inode" that would be
stored in the directory entry down from 62 bytes to 58 bytes.

						- 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