From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Weiner Subject: Re: [PATCH 0/3] bootmem2 III References: <20080509151713.939253437@saeurebad.de> <20080509184044.GA19109@one.firstfloor.org> Date: Sun, 11 May 2008 21:18:09 +0200 In-Reply-To: <20080509184044.GA19109@one.firstfloor.org> (Andi Kleen's message of "Fri, 9 May 2008 20:40:44 +0200") Message-ID: <87lk2gtzta.fsf@saeurebad.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-mm@kvack.org Return-Path: To: Andi Kleen Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, Ingo Molnar , Yinghai Lu , Andrew Morton , Linus Torvalds List-ID: Hi Andi, Andi Kleen 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, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org