Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932330AbZACAcd (ORCPT ); Fri, 2 Jan 2009 19:32:33 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758298AbZACAcY (ORCPT ); Fri, 2 Jan 2009 19:32:24 -0500 Received: from lucidpixels.com ([75.144.35.66]:34548 "EHLO lucidpixels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758216AbZACAcX (ORCPT ); Fri, 2 Jan 2009 19:32:23 -0500 Date: Fri, 2 Jan 2009 19:32:21 -0500 (EST) From: Justin Piszcz To: Arjan van de Ven cc: linux-kernel@vger.kernel.org, Kyle McMartin Subject: Re: 2.6.27/2.6.28: irqbalance dies shortly after starting the daemon on x86 but not x86_64, why? In-Reply-To: <495E93D4.3060401@linux.intel.com> Message-ID: References: <495E93D4.3060401@linux.intel.com> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1119 Lines: 36 On Fri, 2 Jan 2009, Arjan van de Ven wrote: > Justin Piszcz wrote: >> (same on both x86 and x86_64): >> # cat /etc/default/irqbalance >> #Configuration for the irqbalance daemon >> >> #Should irqbalance be enabled? >> ENABLED=1 >> #Balance the IRQs only once? >> ONESHOT="0" > > > which version of irqbalance is this? > $ dpkg -l | grep -i irqbalance ii irqbalance 0.55-2.4 Daemon to balance interrupts for SMP systems Kyle stated: > If there is only one cache domain, ie: one physical cpu socket with two > cores sharing a cache, then irqbalance will return after the initial > balance since it would be pointless to continue running. (It forces > itself into oneshot mode.) The CPU = E6700 so yep, so if there is one physical socket with 4 cores it keeps? For it to keep and not oneshot you need > 2 cores? Justin. -- 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/