From: Jarek Poplawski <jarkao2@gmail.com>
To: Tuomas Jormola <tj@solitudo.net>
Cc: netdev@vger.kernel.org
Subject: Re: PROBLEM: A set of networking related oopses
Date: Sat, 8 Mar 2008 18:57:21 +0100 [thread overview]
Message-ID: <20080308175721.GA3582@ami.dom.local> (raw)
In-Reply-To: <0CFB0535-DE03-4C13-8EC5-9471CED9B6BE@solitudo.net>
On Sat, Mar 08, 2008 at 06:13:55PM +0200, Tuomas Jormola wrote:
...
> (18:08:32)(tj@shakti)(~)$ cat /proc/interrupts
> CPU0 CPU1
...
> 18: 875645 873991 IO-APIC-fasteoi uhci_hcd:usb1,
> uhci_hcd:usb6, eth0
> 19: 2 1 IO-APIC-fasteoi uhci_hcd:usb5, ohci1394
> 20: 0 0 IO-APIC-fasteoi uhci_hcd:usb2
> 21: 0 0 IO-APIC-fasteoi uhci_hcd:usb4,
> ehci_hcd:usb8
> 22: 4 3 IO-APIC-fasteoi heci
> 217: 498561 498427 PCI-MSI-edge eth1
> 218: 88587922 88715380 PCI-MSI-edge ahci
...
> So I would be able to bind eth0 to CPU0 by running
>
> echo 1 > /proc/irq/18/smp_affinity
>
> right? http://www.cs.uwaterloo.ca/~brecht/servers/apic/SMP-affinity.txt
> says that smp affinity only works for drivers that support IO-APIC. The
> eth1 card is an old Intel card, and looks like it doesn't support this. I
> guess I'll replace the card with a newer one.
Should be right. If it's possibile, you can try if moving eth0 to
another slot could give it it's own irq.
I think it should work with both of your cards: eth1 uses newer type
of interrupts - are you sure it's e100?
You can also check if it really fixes the problem by booting with
a kernel parameter: noirqbalance.
Jarek P.
next prev parent reply other threads:[~2008-03-08 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 19:05 PROBLEM: A set of networking related oopses Tuomas Jormola
2008-03-08 9:53 ` Jarek Poplawski
2008-03-08 16:13 ` Tuomas Jormola
2008-03-08 17:57 ` Jarek Poplawski [this message]
2008-03-09 16:58 ` Tuomas Jormola
2008-03-09 17:31 ` Jarek Poplawski
2008-04-24 14:25 ` Tuomas Jormola
2008-04-24 20:01 ` Jarek Poplawski
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=20080308175721.GA3582@ami.dom.local \
--to=jarkao2@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tj@solitudo.net \
/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).