[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080308175721.GA3582@ami.dom.local>
Date: Sat, 8 Mar 2008 18:57:21 +0100
From: Jarek Poplawski <jarkao2@...il.com>
To: Tuomas Jormola <tj@...itudo.net>
Cc: netdev@...r.kernel.org
Subject: Re: PROBLEM: A set of networking related oopses
On Sat, Mar 08, 2008 at 06:13:55PM +0200, Tuomas Jormola wrote:
...
> (18:08:32)(tj@...kti)(~)$ 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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists