Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754958AbZLCQuG (ORCPT ); Thu, 3 Dec 2009 11:50:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754018AbZLCQuD (ORCPT ); Thu, 3 Dec 2009 11:50:03 -0500 Received: from relay1.sgi.com ([192.48.179.29]:45635 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753458AbZLCQuA (ORCPT ); Thu, 3 Dec 2009 11:50:00 -0500 Date: Thu, 3 Dec 2009 10:50:04 -0600 From: Dimitri Sivanich To: Arjan van de Ven Cc: "Eric W. Biederman" , Thomas Gleixner , Peter Zijlstra , Ingo Molnar , Suresh Siddha , Yinghai Lu , LKML , Jesse Barnes , David Miller , Peter P Waskiewicz Jr , "H. Peter Anvin" Subject: Re: [PATCH v6] x86/apic: limit irq affinity Message-ID: <20091203165004.GA14665@sgi.com> References: <20091120211139.GB19106@sgi.com> <20091122011457.GA16910@sgi.com> <1259069986.4531.1453.camel@laptop> <20091124065022.6933be1a@infradead.org> <20091125074033.4c46c1b0@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091125074033.4c46c1b0@infradead.org> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1358 Lines: 30 On Wed, Nov 25, 2009 at 07:40:33AM -0800, Arjan van de Ven wrote: > On Tue, 24 Nov 2009 09:41:18 -0800 > ebiederm@xmission.com (Eric W. Biederman) wrote: > > Oii. > > > > I don't think it is bad to export information to applications like > > irqbalance. > > > > I think it pretty horrible that one of the standard ways I have heard > > to improve performance on 10G nics is to kill irqbalance. > > irqbalance does not move networking irqs; if it does there's something > evil going on in the system. But thanks for the bugreport ;) It does move networking irqs. > > we had that; it didn't work. > what I'm asking for is for the kernel to expose the numa information; > right now that is the piece that is missing. > I'm wondering if we should expose that numa information in the form of a node or the set of allowed cpus, or both? I'm guessing 'both' is the correct answer, so that apps like irqbalance can make a qualitative decision based on the node (affinity to cpus on this node is better), but an absolute decision based on allowed cpus (I cannot change affinity to anything but this set of cpus). -- 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/