From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 26 Apr 2007 09:36:40 -0700 (PDT) From: Christoph Lameter Subject: Re: [PATCH] change global zonelist order on NUMA v3 In-Reply-To: <1177604962.5705.55.camel@localhost> Message-ID: References: <20070426183417.058f6f9e.kamezawa.hiroyu@jp.fujitsu.com> <200704261147.44413.ak@suse.de> <20070426191043.df96c114.kamezawa.hiroyu@jp.fujitsu.com> <20070426195348.6a4e5652.kamezawa.hiroyu@jp.fujitsu.com> <1177603203.5705.36.camel@localhost> <1177604962.5705.55.camel@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: Lee Schermerhorn Cc: KAMEZAWA Hiroyuki , ak@suse.de, linux-kernel@vger.kernel.org, linux-mm@kvack.org, akpm@linux-foundation.org, Eric Whitney List-ID: On Thu, 26 Apr 2007, Lee Schermerhorn wrote: > I have been considering an HP-platform-specific boot option [handled by > a new ia64 machine vec op] to re-distance the interleaved node, but for > other platforms, such as Kame's, I think we still need the ability to > move the DMA zones last in the Normal zone lists. Or, exclude them > altogether? Maybe a solution would be to have a dma_penalty option on boot? The dma penalty is added to the dma zone. If its higher than zero then the dma zone will become a node at that distance to other nodes. The default is zero which would leave it as is. If you boot with dma_penalty=40 then a new slit entry is generated for the DMA zone and its put at that distance. -- 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