| 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: Wed, 4 Apr 2007 09:09:28 -0700 (PDT) From: Linus Torvalds <torvalds@...ux-foundation.org> To: Andrea Arcangeli <andrea@...e.de> cc: Nick Piggin <npiggin@...e.de>, Hugh Dickins <hugh@...itas.com>, Andrew Morton <akpm@...ux-foundation.org>, Linux Memory Management List <linux-mm@...ck.org>, tee@....com, holt@....com, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [rfc] no ZERO_PAGE? On Wed, 4 Apr 2007, Andrea Arcangeli wrote: > > Ok, those cases wanting the same zero page, could be fairly easily > converted to an mmap over /dev/zero (without having to run 4k large > mmap syscalls or nonlinear). You're missing the point. What if it's something like oracle that has been tuned for Linux using this? Or even an open-source app that is just used by big places and they see performace problems but it's not obvious *why*. We "know" why, because we're discussing this point. But two months from now, when some random company complains to SuSE/RH/whatever that their app runs 5% slower or uses 200% more swap, who is going to realize what caused it? THAT is the problem with patches like this. I'm not against it, but you can't just dismiss it with "we can fix the app". We *cannot* fix the app if we don't even realize what caused the problem.. Linus - 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