public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Nyberg <alexn@telia.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.1 dual xeon
Date: Tue, 27 Jan 2004 18:13:07 +0100	[thread overview]
Message-ID: <1075223587.1173.5.camel@llhosts> (raw)
In-Reply-To: <20040127073801.GB9708@favonius>

On Tue, 2004-01-27 at 08:38, Sander wrote:
> 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?

Apparently it was way especially better performance wise to have
interrupts that hit often (ethernet cards ie.) on the same cpu.

But I can't see a reason for not dividing the different interrupt on
different cpu's and letting them stay put. Maybe if you keep all
interrupts on the same cpu the cache on the other ones will not have to
be flushed often, which would be a good thing.

How would it be to maybe remove all interrupts from a cpu (except
between cpu's) and have a few cpu's merely working with data and one "in
control". Bad idea I guess as I haven't seen any such work.

Alex


  reply	other threads:[~2004-01-27 17:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-25  1:36 2.6.1 dual xeon Wakko Warner
2004-01-25  1:43 ` Robert Love
2004-01-25 13:37   ` Wakko Warner
2004-01-27  7:38     ` Sander
2004-01-27 17:13       ` Alexander Nyberg [this message]
2004-01-27 17:41         ` Justin Cormack
2004-01-28  9:32         ` Helge Hafting

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1075223587.1173.5.camel@llhosts \
    --to=alexn@telia.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox