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: <51B8B54D.2040200@sr71.net> Date: Wed, 12 Jun 2013 10:52:13 -0700 From: Dave Hansen <dave@...1.net> To: Dave Hansen <dave.hansen@...el.com>, linux-ext4@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>, Theodore Ts'o <tytso@....edu>, Jan kara <jack@...e.cz>, gnehzuil.liu@...il.com Subject: Re: ext4 extent status tree LRU locking FWIW, I'm also seeing this contention to a much smaller extent on much more "normal" hardware. I've got a 6-core (as opposed to 80) desktop machine where I'm doing the same test on a real disk (instead of a loopback-mounted ramfs file). I'm seeing _about_ 10% CPU time being used on just spinning on the same ext4 LRU lock. -- 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