From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 21 Dec 2002 22:57:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 21 Dec 2002 22:57:28 -0500 Received: from franka.aracnet.com ([216.99.193.44]:30089 "EHLO franka.aracnet.com") by vger.kernel.org with ESMTP id ; Sat, 21 Dec 2002 22:57:28 -0500 Date: Sat, 21 Dec 2002 20:05:18 -0800 From: "Martin J. Bligh" To: "Pallipadi, Venkatesh" , William Lee Irwin III , "Protasevich, Natalie" cc: Christoph Hellwig , James Cleverdon , Linux Kernel , John Stultz , "Nakajima, Jun" , "Mallick, Asit K" , "Saxena, Sunil" , "Van Maren, Kevin" , Andi Kleen , Hubert Mantel , "Kamble, Nitin A" Subject: RE: [PATCH][2.4] generic cluster APIC support for systems with m ore than 8 CPUs Message-ID: <6470000.1040529916@titus> In-Reply-To: References: X-Mailer: Mulberry/2.2.1 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > Yes, our feeling it is possible to handle all non-NUMAQ systems pretty > generically in terms of APIC setup and interrupt routing. We can use > either logical clustered or physical destination modes. But for NUMAQ > systems, interrupt routing has to know about the local nodes and have > necessary logic to do the routing withing local node. NUMA-Q doesn't have to know about the local nodes. I set it up to use physical delivery broadcast, which is a node-local broadcast ... gave me NUMA affinity for free. I could also use logical clustered (p3 style) addressing, and work out all the node locality, but I don't see the point. M.