public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Joerg Sommrey <jo@sommrey.de>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Question on CONFIG_IRQBALANCE / 2.6.x
Date: Fri, 18 Feb 2005 18:11:17 -0500	[thread overview]
Message-ID: <42167615.5080906@pobox.com> (raw)
In-Reply-To: <20050218225722.GA11292@sommrey.de>

Joerg Sommrey wrote:
> On Fri, Feb 18, 2005 at 02:39:49PM -0800, Martin J. Bligh wrote:
> 
>>>there's something I don't understand:  With IRQBALANCE *enabled* almost
>>>all interrupts are processed on CPU0.  This changed in an unexpected way
>>>after disabling IRQBALANCE: now all interrupts are distributed uniformly
>>>to both CPUs.  Maybe it's intentional, but it's not what I expect when a
>>>config option named IRQBALANCE is *disabled*.
>>>
>>>Can anybody comment on this?
>>
>>If you have a Pentium 3 based system, by default they'll round robin.
>>If you turn on IRQbalance, they won't move until the traffic gets high
>>enough load to matter. That's presumably what you're seeing.
> 
> 
> It's an Athlon box that propably has the same behaviour.  Just another
> question on this topic:  with IRQBALANCE enabled, almost all interupts
> are routet to CPU0.  Lately irq 0 runs on CPU1 and never returns to CPU0
> - is there any obvious reason for that?

Note that it is a popular recommendation to -disable- CONFIG_IRQBALANCE, 
and then run the userspace 'irqbalanced'.

	Jeff




  reply	other threads:[~2005-02-18 23:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-18 21:33 Question on CONFIG_IRQBALANCE / 2.6.x Joerg Sommrey
2005-02-18 22:39 ` Martin J. Bligh
2005-02-18 22:57   ` Joerg Sommrey
2005-02-18 23:11     ` Jeff Garzik [this message]
2005-02-20 14:41     ` Martin J. Bligh

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=42167615.5080906@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=jo@sommrey.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox