From: Len Brown <len.brown@intel.com>
To: Julien Oster <lkml-2315@mc.frodoid.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: balance interrupts
Date: 08 Dec 2003 16:46:24 -0500 [thread overview]
Message-ID: <1070919984.2551.116.camel@dhcppc4> (raw)
In-Reply-To: <frodoid.frodo.8765grkrkb.fsf@usenet.frodoid.org>
This is a tight squeeze. The system has 13 PCI interrupt inputs, but
the chip-set has only a single IO-APIC with 8-pins to handle them.
You don't see all the interrupts in /proc/interrupts because there are
not device drivers attached to all of them -- but if you edit them in
from lspci output you'd get this:
0: 40022145 IO-APIC-edge timer
1: 62950 IO-APIC-edge i8042
2: 0 XT-PIC cascade
8: 681626 IO-APIC-edge rtc
9: 0 IO-APIC-level acpi
12: 55 IO-APIC-edge i8042
14: 968274 IO-APIC-edge ide0
15: 1789182 IO-APIC-edge ide1
16: 404489 IO-APIC-level EMU10K1, eth2
17: eth3
18: 445160 IO-APIC-level ide2, ide3, eth0
19: 1596427 IO-APIC-level eth1, matrox
20: 0 IO-APIC-level ohci_hcd
21: 0 IO-APIC-level NVidia nForce2 audio, usb
22: 36730 IO-APIC-level ohci_hcd, audio
23: smbus
No, the siimage appears to be a single pci device, so you'll not get to
split ide2 and ide3.
The ethernets appears to be a quad DEC ethernet card with a PCI bridge.
You're using eth0 and eth1. But if you used eth3 instead of eth0, you'd
have an ethernet I/F with an interrupt all to itself.
cheers,
-Len
ps. yes, the AML shows these interrupt links are programmable, but it is
unclear if the BIOS/hardware is capable of programming any of the PCI
interrupts to unused destinations < 16 when in APIC mode.
I'd be interested to see the dmesg -s40000 for this box.
pps low hanging fruit = easy to pick
ppps high rent district = expensive place to live
next prev parent reply other threads:[~2003-12-08 21:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BF1FE1855350A0479097B3A0D2A80EE00184D619@hdsmsx402.hd.intel.com>
2003-12-08 19:29 ` balance interrupts Len Brown
2003-12-08 20:00 ` Julien Oster
2003-12-08 20:02 ` Julien Oster
2003-12-08 21:46 ` Len Brown [this message]
2003-12-09 3:51 ` Bob
2003-12-09 5:11 ` Stephen Satchell
2003-12-09 13:19 ` Swap performance statistics in 2.6 -- which /proc file has it? Stephen Satchell
2003-12-09 13:56 ` Richard B. Johnson
2003-12-09 14:46 ` Stephen Satchell
2003-12-09 15:25 ` Richard B. Johnson
2003-12-09 19:53 ` Dominik Kubla
2003-12-09 20:24 ` Richard B. Johnson
2003-12-10 10:18 ` Dominik Kubla
2003-12-10 1:28 ` Stephen Satchell
2003-12-10 10:34 ` Dominik Kubla
2003-12-10 13:06 ` Answer to Swap performance statistics in 2.6 -- which /proc file has it Stephen Satchell
2003-12-08 17:59 balance interrupts Julien Oster
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=1070919984.2551.116.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml-2315@mc.frodoid.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