Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261270AbUA0HiE (ORCPT ); Tue, 27 Jan 2004 02:38:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262687AbUA0HiE (ORCPT ); Tue, 27 Jan 2004 02:38:04 -0500 Received: from ookhoi.xs4all.nl ([213.84.114.66]:53890 "EHLO favonius.humilis.net") by vger.kernel.org with ESMTP id S261270AbUA0HiC (ORCPT ); Tue, 27 Jan 2004 02:38:02 -0500 Date: Tue, 27 Jan 2004 08:38:01 +0100 From: Sander To: Wakko Warner Cc: Robert Love , linux-kernel@vger.kernel.org Subject: Re: 2.6.1 dual xeon Message-ID: <20040127073801.GB9708@favonius> Reply-To: sander@humilis.net References: <20040124203646.A8709@animx.eu.org> <1074995006.5246.1.camel@localhost> <20040125083712.A9318@animx.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040125083712.A9318@animx.eu.org> X-Uptime: 07:25:48 up 31 days, 21:14, 36 users, load average: 1.16, 1.99, 2.45 User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 990 Lines: 25 Wakko Warner wrote (ao): > > > I recently aquired a dual xeon system. HT is enabled which shows > > > up as 4 cpus. I noticed that all interrupts are on CPU0. Can > > > anyone tell me why this is? > > > > The APIC needs to be programmed to deliver interrupts to certain > > processors. > > > > In 2.6, this is done in user-space via a program called irqbalance: > > Thanks, working great. (Debian by the way) Ehm, IIRC the "all interrupts are on CPU0" is how it is supposed to work with a 2.6 kernel? The interrupts should spread if you have _a_lot_ of them. This gives better performance than spreading the interrupts. Did I read this on the list, or am I completely wrong here? -- Humilis IT Services and Solutions http://www.humilis.net - 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/