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
| ||
|
Message-ID: <20131002162323.GB31579@thunk.org> Date: Wed, 2 Oct 2013 12:23:23 -0400 From: Theodore Ts'o <tytso@....edu> To: Eric Sandeen <sandeen@...hat.com> Cc: Jan Kara <jack@...e.cz>, Benjamin LaHaise <bcrl@...ck.org>, Andreas Dilger <adilger.kernel@...ger.ca>, linux-ext4@...r.kernel.org Subject: Re: [PATCH] ext4: add noorlov parameter to avoid spreading of directory inodes On Wed, Oct 02, 2013 at 10:02:12AM -0500, Eric Sandeen wrote: > One thing I'm curious about - what changed from ext3 to ext4? I thought > both defaulted to orlov and the same type of allocation behavior, more > or less. I guess one change is that the "oldalloc" mount > option went away. Ext3 used an orlov style allocator as well. The main difference between ext4 and ext3 is the orlov allocator is now done on a per-flexbg basis instead of per-blockgroup basis. That is, we do the statistics based on a flex-bg basis instead of the blockgroup basis. As a result, I suspect Ben would see the inode allocation behavior equivalent to ext3 if he creates the file system using "mke2fs -t ext4 -G 1" to force the flex_bg size to 1. Can you let me know what the size of the file system was, and mke2fs parameters you were using for ext3 and ext4? I have a feeling that inode allocations weren't optimal for your use case even with ext3, but because we now spread the inodes based on flex_bg's instead of block groups, that's why you saw the performance degredation. - 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
Powered by blists - more mailing lists