From: Andi Kleen <ak@muc.de>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel@vger.kernel.org, jun.nakajima@intel.com
Subject: Re: CONFIG_IRQBALANCE for AMD64?
Date: Fri, 28 May 2004 23:45:11 +0200 [thread overview]
Message-ID: <m3hdu08bvc.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <20UqZ-7i7-5@gated-at.bofh.it> (Martin J. Bligh's message of "Fri, 28 May 2004 20:40:09 +0200")
"Martin J. Bligh" <mbligh@aracnet.com> writes:
> Whatever we do ... all arches are going to need to provide a way to direct
> interrupts to a certain CPU, or group thereof. Can they all do that already?
> I'll confess to not having looked at non-i386 arches. And are others as
> brain damaged as the P4? or do they do something round-robin by default?
I wouldn't really blame the the P4, it's the IO-APICs in the chipsets
that balance or not balance.
At least the AMD chipsets found in most Opteron boxes need software
balancing too.
-Andi
next parent reply other threads:[~2004-05-28 21:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2004-05-28 23:37 CONFIG_IRQBALANCE for AMD64? Nakajima, Jun
-- strict thread matches above, loose matches on Subject: below --
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
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-28 17:09 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
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=m3hdu08bvc.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=jun.nakajima@intel.com \
--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 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.