All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Joe Korty <joe.korty@ccur.com>
Cc: Ethan Weinstein <lists@stinkfoot.org>,
	linux-kernel@vger.kernel.org,
	William Lee Irwin III <wli@holomorphy.com>
Subject: Re: 2.6.1 and irq balancing
Date: Sun, 11 Jan 2004 19:19:32 +0100	[thread overview]
Message-ID: <20040111181932.GA6192@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040111165012.GA24746@tsunami.ccur.com>

[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]

On Sun, Jan 11, 2004 at 11:50:12AM -0500, Joe Korty wrote:
> On Sun, Jan 11, 2004 at 10:51:22AM +0100, Arjan van de Ven wrote:
> > On Sun, 2004-01-11 at 00:14, Ethan Weinstein wrote:
> > > Greetings all,
> > > 
> > > I upgraded my server to 2.6.1, and I'm finding I'm saddled with only 
> > > interrupting on CPU0 again. 2.6.0 does this as well. This is the 
> > > Supermicro X5DPL-iGM-O (E7501 chipset), 2 Xeons@2.4ghz HT enabled. 
> > > /proc/cpuinfo is normal as per HT, displaying 4 cpus.
> > 
> > you should run the userspace irq balance daemon:
> > http://people.redhat.com/arjanv/irqbalance/
> 
> I have long wondered what is so evil about most interrupts going to
> CPU 0 that we felt we had to have a pair of irqdaemons in 2.6.

well irqbalanced is a userspace balancer

> Earlier APICs had a variation where the search for where each new
> interrupt was to go started with first cpu after the one that got the
> last interrupt.  If we call this 'round-robin' allocation, then today's
> technique could be described as 'first fit'.

if it's really busy it starves cpu0 .... 

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-01-11 18:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-10 23:14 2.6.1 and irq balancing Ethan Weinstein
2004-01-11  2:39 ` Ed Tomlinson
2004-01-11  3:38   ` Nick Piggin
2004-01-11  9:52     ` Arjan van de Ven
2004-01-11  5:19   ` Ethan Weinstein
2004-01-11  9:51 ` Arjan van de Ven
2004-01-11 16:50   ` Joe Korty
2004-01-11 18:19     ` Arjan van de Ven [this message]
2004-01-15 11:43     ` Pavel Machek
2004-01-11 13:14 ` Martin Schlemmer
  -- strict thread matches above, loose matches on Subject: below --
2004-01-11 23:59 Nakajima, Jun
2004-01-12  4:42 ` Bill Davidsen
2004-01-12 14:06   ` Zwane Mwaikambo
2004-01-12 16:10   ` Martin J. Bligh
2004-01-13  6:50 ` Ethan Weinstein
2004-01-13  7:05   ` Nick Piggin
2004-01-13  7:57 Nakajima, Jun
2004-01-13  8:09 Nakajima, Jun

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=20040111181932.GA6192@devserv.devel.redhat.com \
    --to=arjanv@redhat.com \
    --cc=joe.korty@ccur.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@stinkfoot.org \
    --cc=wli@holomorphy.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.