From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: IRQ splitting
Date: Thu, 5 Apr 2007 10:14:26 -0400 [thread overview]
Message-ID: <20070405141426.GE3510@csclub.uwaterloo.ca> (raw)
In-Reply-To: <Pine.LNX.4.61.0704051231280.22282@yvahk01.tjqt.qr>
On Thu, Apr 05, 2007 at 12:40:57PM +0200, Jan Engelhardt wrote:
> let's take the following /proc/interrupts dump (CPU2,CPU3 trimmed)...
>
> CPU0 CPU1
> 0: 37041766 37038991 IO-APIC-edge timer
> 1: 10 2 IO-APIC-edge i8042
> 8: 0 0 IO-APIC-edge rtc
> 9: 0 0 IO-APIC-level acpi
> 12: 114 0 IO-APIC-edge i8042
> 14: 25219 5800049 IO-APIC-edge ide0
> 201: 260381 238454 IO-APIC-level aacraid
> 209: 0 0 IO-APIC-level ohci_hcd:usb1
> 217: 0 0 IO-APIC-level ehci_hcd:usb2
> 225: 57531742 0 IO-APIC-level eth0,radeon@pci:0000:03:00.0
> 233: 26 0 IO-APIC-level eth1
> NMI: 1661 1397
> LOC: 147579966 147579949
> ERR: 0
> MIS: 0
>
> My question is whether it is possible that eth0's interrupts go to CPU0
> and radeon's to CPU1, and if so, how I would enable that. Alternatively,
> is it possible to just move eth0 or radeon to a different interrupt?
Check the motherboard manual. Sometimes they explictly list which slots
share IRQs (And by share I mean are physically tied to the same wire).
I know many Asus boards have that information in the manual.
So in many cases other than changing slots, there is nothing you can do
to change the IRQ sharing, since the slots are physically sharing the
interrupt.
--
Len Sorensen
next prev parent reply other threads:[~2007-04-05 14:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 10:40 Jan Engelhardt
2007-04-05 12:13 ` Jiri Kosina
2007-04-05 13:11 ` Mark Hounschell
2007-04-05 14:14 ` Lennart Sorensen [this message]
[not found] <fa.21iotKLTgoLpkKhrbSxrjy5v7hM@ifi.uio.no>
2007-04-05 14:34 ` Robert Hancock
2007-04-05 19:23 ` Stephen Hemminger
2007-04-05 20:37 ` Jan Engelhardt
2007-04-05 19:45 ` Stephen Hemminger
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=20070405141426.GE3510@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®