From: Julien Oster <lkml-2315@mc.frodoid.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: balance interrupts
Date: Mon, 08 Dec 2003 18:59:36 +0100 [thread overview]
Message-ID: <frodoid.frodo.87zne3tcl3.fsf@usenet.frodoid.org> (raw)
Hello!
Now that my IO-APIC finally works without lockups (thanks to all!) on
my nforce2 boards, my interrupts are much less crowded. However,
there's still one line in /proc/interrupts which I don't really like,
it's also the only line where more than one piece of hardware shares
the same interrupt:
18: 445160 IO-APIC-level ide2, ide3, eth0
ide2 and ide3 are my onboard Silicon Image SATA controller. I guess
you can't keep them apart on to different interrupts, since it's only
one chip which is most probably connected to one IRQ line only.
But I don't think that eth0 has to be on the same interrupt as my SATA
controller. So, how do I make it go away to another place? I would be
fine sharing it with e.g. eth1, which is alone on IRQ 19.
BTW, the whole /proc/interrupts looks like this:
CPU0
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
18: 445160 IO-APIC-level ide2, ide3, eth0
19: 1596427 IO-APIC-level eth1
20: 0 IO-APIC-level ohci_hcd
21: 0 IO-APIC-level NVidia nForce2
22: 36730 IO-APIC-level ohci_hcd
NMI: 0
LOC: 40021891
ERR: 0
MIS: 310
Regards,
Julien
next reply other threads:[~2003-12-08 18:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 17:59 Julien Oster [this message]
[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
2003-12-09 3:51 ` Bob
2003-12-09 5:11 ` Stephen Satchell
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=frodoid.frodo.87zne3tcl3.fsf@usenet.frodoid.org \
--to=lkml-2315@mc.frodoid.org \
--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;
as well as URLs for NNTP newsgroup(s).