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
| ||
|
Date: Sat, 4 Aug 2007 23:03:51 +0200 From: Ingo Molnar <mingo@...e.hu> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: J??rn Engel <joern@...fs.org>, Jeff Garzik <jeff@...zik.org>, Linus Torvalds <torvalds@...ux-foundation.org>, Peter Zijlstra <a.p.zijlstra@...llo.nl>, linux-mm@...ck.org, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, miklos@...redi.hu, akpm@...ux-foundation.org, neilb@...e.de, dgc@....com, tomoki.sekiyama.qu@...achi.com, nikita@...sterfs.com, trond.myklebust@....uio.no, yingchao.zhou@...il.com, richard@....demon.co.uk, david@...g.hm Subject: Re: [PATCH 00/23] per device dirty throttling -v8 * Ingo Molnar <mingo@...e.hu> wrote: > noatime,nodiratime gave 50% of wall-clock kernel rpm build performance > improvement for Dave Jones, on a beefy box. Unless i misunderstood > what you meant under 'fraction of a percent' your numbers are _WAY_ > off. Atime updates are a _huge everyday deal_, from laptops to > servers. Everywhere on the planet. Give me a Linux desktop anywhere > and i can tell you whether it has atimes on or off, just by clicking > around and using apps (without looking at the mount options). That's > how i notice it that i forgot to turn off atime on any newly installed > system - the system has weird desktop lags and unnecessary disk > trashing. i cannot over-emphasise how much of a deal it is in practice. Atime updates are by far the biggest IO performance deficiency that Linux has today. Getting rid of atime updates would give us more everyday Linux performance than all the pagecache speedups of the past 10 years, _combined_. it's also perhaps the most stupid Unix design idea of all times. Unix is really nice and well done, but think about this a bit: ' For every file that is read from the disk, lets do a ... write to the disk! And, for every file that is already cached and which we read from the cache ... do a write to the disk! ' tell that concept to any rookie programmer who knows nothing about kernels and the answer will be: 'huh, what? That's gross!'. And Linux does this unconditionally for everything, and no, it's not only done on some high-security servers that need all sorts of auditing enabled that logs every file read - no, it's done by 99% of the Linux desktops and servers. For the sake of some lazy mailers that could now be using inotify, and for the sake of ... nothing much, really - forensics software perhaps. Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists