public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
	Jeff Garzik <jgarzik@pobox.com>,
	"Nakajima, Jun" <jun.nakajima@intel.com>,
	Andrew Morton <akpm@osdl.org>, Anton Blanchard <anton@samba.org>,
	linux-kernel@vger.kernel.org
Subject: Re: CONFIG_IRQBALANCE for AMD64?
Date: Fri, 28 May 2004 22:03:28 +0200	[thread overview]
Message-ID: <20040528200328.GJ9898@devserv.devel.redhat.com> (raw)
In-Reply-To: <40B7984E.7040208@us.ibm.com>

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

On Fri, May 28, 2004 at 12:51:42PM -0700, Nivedita Singhvi wrote:
> The irqbalanced is a user space daemon that attempts to
> balance irqs across CPUs. It keeps track of the current
> irq counts on the CPUs, and at regular intervals applies
> changes to irq binding in order to implement the desired
> policy. It achieves a high-level long term balance of irqs
> across CPUs.
> 
> This is a fairly expensive but generally arch independent
> (as long as they support cpu binding of irqs) method to
> achieve long term distribution of interrupts.

it's not THAT expensive. Really.


> I think this is best used for fairly balanced (over time)
> long running workloads. For short workloads which demonstrate
> intense activity in bursts, this won't be as effective.

intense bursts average out... and to be honest, in bursts the last thing you
want to do is move it to different cpus all the time since then you get so
much cross cpu cache misses and you are far slower....


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

  parent reply	other threads:[~2004-05-28 20:04 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28 17:09 CONFIG_IRQBALANCE for AMD64? Nakajima, Jun
2004-05-28 17:40 ` Jeff Garzik
2004-05-28 17:45   ` Arjan van de Ven
2004-05-28 17:46   ` Martin J. Bligh
2004-05-28 17:57     ` Arjan van de Ven
2004-05-28 19:51       ` Nivedita Singhvi
2004-05-28 19:58         ` Jeff Garzik
2004-05-28 20:14           ` Nivedita Singhvi
2004-05-28 21:45             ` Jeff Garzik
2004-05-28 20:03         ` Arjan van de Ven [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-28 23:37 Nakajima, Jun
2004-05-28 22:05 Nakajima, Jun
2004-05-28 22:54 ` Andi Kleen
2004-05-29  1:27   ` Nick Piggin
2004-05-29 10:06     ` Andi Kleen
2004-05-29 10:10       ` Nick Piggin
2004-05-29 11:18         ` Andi Kleen
     [not found] <20Uhn-7bP-11@gated-at.bofh.it>
     [not found] ` <20UqZ-7i7-5@gated-at.bofh.it>
2004-05-28 21:45   ` Andi Kleen
2004-05-28 18:20 Nakajima, Jun
2004-05-28 18:33 ` Martin J. Bligh
2004-05-28 18:44   ` Arjan van de Ven
2004-05-28 18:57     ` Martin J. Bligh
2004-05-28 19:01       ` Arjan van de Ven
2004-05-29  8:38     ` michael
2004-05-29  8:41     ` michael
2004-05-29  8:45       ` Arjan van de Ven
2004-05-27  3:48 Thomas Zehetbauer
2004-05-27  5:13 ` Jeff Garzik
2004-05-27 16:36   ` Thomas Zehetbauer
2004-05-27 16:50     ` Arjan van de Ven
2004-05-27 21:37       ` Chris Wedgwood
2004-05-27 17:03     ` Anton Blanchard
2004-05-27 22:36       ` Thomas Zehetbauer
2004-05-28  5:57         ` Arjan van de Ven

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=20040528200328.GJ9898@devserv.devel.redhat.com \
    --to=arjanv@redhat.com \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=jgarzik@pobox.com \
    --cc=jun.nakajima@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=niv@us.ibm.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