From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 26 Jul 2007 11:03:59 -0700 (PDT) From: Christoph Lameter Subject: Re: NUMA policy issues with ZONE_MOVABLE In-Reply-To: <20070726161652.GA16556@skynet.ie> Message-ID: References: <20070725111646.GA9098@skynet.ie> <20070726131539.8a05760f.kamezawa.hiroyu@jp.fujitsu.com> <20070726161652.GA16556@skynet.ie> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: Mel Gorman Cc: KAMEZAWA Hiroyuki , linux-mm@kvack.org, Lee Schermerhorn , ak@suse.de, akpm@linux-foundation.org, pj@sgi.com List-ID: On Thu, 26 Jul 2007, Mel Gorman wrote: > /* policy_zone is the lowest zone index that is present on all nodes */ > > Right? Nope. In a 4 node x86_64 opteron configuration with 8GB memory in 4 2GB chunks you could have node 0 ZONE_DMA, ZONE_DMA32 <2GB node 1 ZONE_DMA32 <4GB node 2 ZONE_NORMAL <6GB node 3 ZONE_NORMAL <8GB So the highest zone gets partitioned off? We only have ZONE_MOVABLE on nodes 2 and 3? There are some other weirdnesses possible with ZONE_MOVABLE on !NUMA. 1GB i386 system ZONE_DMA ZONE_NORMAL <900k ZONE_HIGHEMEM 100k size ZONE_MOVABLE can then only use 100k? -- 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