From: Arjan van de Ven <arjanv@redhat.com>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Ed Tomlinson <edt@aei.ca>,
linux-kernel@vger.kernel.org,
Ethan Weinstein <lists@stinkfoot.org>
Subject: Re: 2.6.1 and irq balancing
Date: Sun, 11 Jan 2004 10:52:03 +0100 [thread overview]
Message-ID: <1073814722.4431.7.camel@laptop.fenrus.com> (raw)
In-Reply-To: <4000C544.1040301@cyberone.com.au>
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
On Sun, 2004-01-11 at 04:38, Nick Piggin wrote:
> Ed Tomlinson wrote:
>
> >Hi,
> >
> >What is the load on the box when this is happening? If its low think
> >this is optimal (for cache reasons).
> >
> >
>
> I'd rather see different interrupt sources run on different CPUs
> initially, which would help fairness a little bit, and should be
> more optimal with big interrupt loads.
>
>
> 0: xxx1 0 0 0
> 1: 0 xxx2 0 0
> 2: 0 0 xxx3 0
> 3: 0 0 0 xxx4
>
> This would delay the need for interrupt balancing in the case where
> 2 or more interrupts are heavily used.
this is what irqbalanced will do (but more inteligent than just using
the irq number as round robin seed).
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-11 9:52 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 [this message]
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
2004-01-15 11:43 ` Pavel Machek
2004-01-11 13:14 ` Martin Schlemmer
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=1073814722.4431.7.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=edt@aei.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@stinkfoot.org \
--cc=piggin@cyberone.com.au \
/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;
as well as URLs for NNTP newsgroup(s).