| 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: <87lk2gtzta.fsf@saeurebad.de> Date: Sun, 11 May 2008 21:18:09 +0200 From: Johannes Weiner <hannes@...urebad.de> To: Andi Kleen <andi@...stfloor.org> Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org, Ingo Molnar <mingo@...e.hu>, 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 Hi Andi, Andi Kleen <andi@...stfloor.org> writes: > 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. Hm, that would put the logic into arch-code. I have no strong opinion about it. > That said the bootmem code has gotten a little crufty and a clean > rewrite might be a good idea. I agree completely. Hannes -- 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