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: Fri, 9 May 2008 20:40:44 +0200 From: Andi Kleen <andi@...stfloor.org> To: Johannes Weiner <hannes@...urebad.de> Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org, Ingo Molnar <mingo@...e.hu>, Andi Kleen <andi@...stfloor.org>, Yinghai Lu <yhlu.kernel@...il.com>, Andrew Morton <akpm@...ux-foundation.org>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: [PATCH 0/3] bootmem2 III On Fri, May 09, 2008 at 05:17:13PM +0200, Johannes Weiner wrote: > here is bootmem2, a memory block-oriented boot time allocator. > > Recent NUMA topologies broke the current bootmem's assumption that > memory nodes provide non-overlapping and contiguous ranges of pages. I'm still not sure that's a really good rationale for bootmem2. e.g. the non continuous nodes are really special cases and there tends to be enough memory at the beginning which is enough for boot time use, so for those systems it would be quite reasonably to only put the continuous starts of the nodes into bootmem. That said the bootmem code has gotten a little crufty and a clean rewrite might be a good idea. -Andi -- 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