| 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: Thu, 11 Jan 2007 19:12:07 +1100 From: Nick Piggin <nickpiggin@...oo.com.au> To: Aubrey <aubreylee@...il.com> CC: Andrew Morton <akpm@...l.org>, Linus Torvalds <torvalds@...l.org>, Hua Zhong <hzhong@...il.com>, Hugh Dickins <hugh@...itas.com>, linux-kernel@...r.kernel.org, hch@...radead.org, kenneth.w.chen@...el.com, mjt@....msk.ru Subject: Re: O_DIRECT question Aubrey wrote: > On 1/11/07, Nick Piggin <nickpiggin@...oo.com.au> wrote: >> What you _really_ want to do is avoid large mallocs after boot, or use >> a CPU with an mmu. I don't think nommu linux was ever intended to be a >> simple drop in replacement for a normal unix kernel. > > > Is there a position available working on mmu CPU? Joking, :) > Yes, some problems are serious on nommu linux. But I think we should > try to fix them not avoid them. Exactly, and the *real* fix is to modify userspace not to make > PAGE_SIZE mallocs[*] if it is to be nommu friendly. It is the kernel hacks to do things like limit cache size that are the bandaids. Of course, being an embedded system, if they work for you then that's really fine and you can obviously ship with them. But they don't need to go upstream. -- SUSE Labs, Novell Inc. Send instant messages to your online friends http://au.messenger.yahoo.com - 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