From mboxrd@z Thu Jan 1 00:00:00 1970 From: jbarnes@sgi.com (Jesse Barnes) Date: Wed, 25 Feb 2004 16:54:09 +0000 Subject: Re: fix zonelist ordering for NUMA Message-Id: <20040225165409.GB20253@sgi.com> List-Id: References: <20040224.182028.884032071.nomura@linux.bs1.fc.nec.co.jp> In-Reply-To: <20040224.182028.884032071.nomura@linux.bs1.fc.nec.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-ia64@vger.kernel.org On Wed, Feb 25, 2004 at 02:01:16PM +0900, j-nomura@ce.jp.nec.com wrote: > > 1) make it arch independent > > this means having arch code populate a SLIT-like table for use by > > the generic zonelist building code > > I would like to hear the comments from people on other arch. > If the same ordering rule can be applicable for others, it's nice. Martin, does a scheme like this sound ok with you? Arch specific code would populate a node distance table, which would be used to build each pgdat->zonelist in a smarter way than we do currently. > > 2) handle the cases that Erich talked about a bit better > > 3) some systems have pgdats w/o any CPUs associated with them, they > > need to be dealt with differently than regular nodes, maybe as > > extensions to an existing node > > > > The final routine might look something like (many thanks to pj for > > hitting me with a cluebat about this): > > It looks cleaner than mine. I'll try it. Cool, thanks. Jesse