Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 20 Jan 2003 14:50:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 20 Jan 2003 14:49:15 -0500 Received: from e3.ny.us.ibm.com ([32.97.182.103]:23707 "EHLO e3.ny.us.ibm.com") by vger.kernel.org with ESMTP id convert rfc822-to-8bit; Mon, 20 Jan 2003 14:48:09 -0500 Content-Type: text/plain; charset=US-ASCII From: Andrew Theurer To: "Martin J. Bligh" , Ingo Molnar Subject: Re: [patch] sched-2.5.59-A2 Date: Mon, 20 Jan 2003 13:52:55 -0600 User-Agent: KMail/1.4.3 Cc: Erich Focht , Michael Hohnbaum , Matthew Dobson , Christoph Hellwig , Robert Love , Linus Torvalds , linux-kernel , lse-tech , Anton Blanchard References: <200301201313.39621.habanero@us.ibm.com> <262510000.1043091224@flay> In-Reply-To: <262510000.1043091224@flay> MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Message-Id: <200301201352.55534.habanero@us.ibm.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > > I have included a very rough patch to do ht-numa topology. I requires to > > manually define CONFIG_NUMA and CONFIG_NUMA_SCHED. It also uses > > num_cpunodes instead of numnodes and defines MAX_NUM_NODES to 8 if > > CONFIG_NUMA is defined. > > Whilst it's fine for benchmarking, I think this kind of overlap is a > very bad idea long-term - the confusion introduced is just asking for > trouble. And think what's going to happen when you mix HT and NUMA. > If we're going to use this for HT, it needs abstracting out. I have no issues with using HT specific bits instead of NUMA. Design wise it would be nice if it could all be happy together, but if not, then so be it. -Andrew Theurer - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/