From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261791AbULUQ2B (ORCPT ); Tue, 21 Dec 2004 11:28:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261788AbULUQ1l (ORCPT ); Tue, 21 Dec 2004 11:27:41 -0500 Received: from omx1-ext.sgi.com ([192.48.179.11]:37601 "EHLO omx1.americas.sgi.com") by vger.kernel.org with ESMTP id S261787AbULUQYc (ORCPT ); Tue, 21 Dec 2004 11:24:32 -0500 Date: Tue, 21 Dec 2004 10:23:59 -0600 From: Brent Casavant Reply-To: Brent Casavant To: Anton Blanchard cc: "Jose R. Santos" , Andi Kleen , "Martin J. Bligh" , linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-ia64@vger.kernel.org Subject: Re: [PATCH 0/3] NUMA boot hash allocation interleaving In-Reply-To: <20041221114605.GB21710@krispykreme.ozlabs.ibm.com> Message-ID: References: <50260000.1103061628@flay> <20041215045855.GH27225@wotan.suse.de> <20041215144730.GC24000@krispykreme.ozlabs.ibm.com> <20041216050248.GG32718@wotan.suse.de> <20041216051323.GI24000@krispykreme.ozlabs.ibm.com> <20041216141814.GA10292@rx8.austin.ibm.com> <20041220165629.GA21231@rx8.austin.ibm.com> <20041221114605.GB21710@krispykreme.ozlabs.ibm.com> Organization: "Silicon Graphics, Inc." MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 21 Dec 2004, Anton Blanchard wrote: > > The difference between the two runs was with in noise of the benchmark on > > my small setup. I wont be able to get a larger NUMA system until next year, > > so I'll retest when that happens. In the mean time, I don't see a reason > > either to stall this patch, but that may change on I get numbers on a > > larger system. > > Thanks Jose! > > Brent, looks like we are happy on the ppc64 front. I didn't realize this was ppc64 testing. What was the exact setup for the testing? The patch as posted (and I hope clearly explained) only turns on the behavior by default when both CONFIG_NUMA and CONFIG_IA64 were active. It could be activated on non-IA64 by setting hashdist=1 on the boot line, or by modifying the patch. I would hate to find out that the testing didn't actually enable the new behavior. Thanks, Brent -- Brent Casavant If you had nothing to fear, bcasavan@sgi.com how then could you be brave? Silicon Graphics, Inc. -- Queen Dama, Source Wars