[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A182A08.9050305@googlemail.com>
Date: Sat, 23 May 2009 18:53:28 +0200
From: Michael Riepe <michael.riepe@...glemail.com>
To: David Dillow <dave@...dillows.org>
CC: Michael Buesch <mb@...sch.de>,
Francois Romieu <romieu@...zoreil.com>,
Rui Santos <rsantos@...popie.com>,
Michael Büker <m.bueker@...lin.de>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH 2.6.30-rc4] r8169: avoid losing MSI interrupts
David Dillow wrote:
> On Sat, 2009-05-23 at 18:12 +0200, Michael Riepe wrote:
>
>>If I use two connections (iperf -P2) and nail iperf to both threads of a
>>single core with taskset (the program is multi-threaded, just in case
>>you wonder), I get this:
>>
>>CPU 0+2: 0.0-60.0 sec 4.65 GBytes 665 Mbits/sec
>>CPU 1+3: 0.0-60.0 sec 6.43 GBytes 920 Mbits/sec
>>
>>That's quite a difference, isn't it?
>>
>>Now I wonder what CPU 0 is doing...
>
>
> Where does /proc/interrupts say the irqs are going?
Oh well...
CPU0 CPU1 CPU2 CPU3
0: 66 0 0 0 IO-APIC-edge timer
1: 2 0 0 0 IO-APIC-edge i8042
7: 0 0 0 0 IO-APIC-edge
parport0
8: 1 0 0 0 IO-APIC-edge rtc0
9: 0 0 0 0 IO-APIC-fasteoi acpi
12: 4 0 0 0 IO-APIC-edge i8042
14: 0 0 0 0 IO-APIC-edge
ata_piix
15: 0 0 0 0 IO-APIC-edge
ata_piix
16: 0 0 0 0 IO-APIC-fasteoi
uhci_hcd:usb4
18: 0 0 0 0 IO-APIC-fasteoi
uhci_hcd:usb3
19: 9696 0 0 0 IO-APIC-fasteoi
ata_piix, uhci_hcd:usb2
22: 471 0 0 0 IO-APIC-fasteoi HDA
Intel
23: 100 0 0 0 IO-APIC-fasteoi
uhci_hcd:usb1, ehci_hcd:usb5
27: 48463995 0 0 0 PCI-MSI-edge eth0
NMI: 0 0 0 0 Non-maskable interrupts
LOC: 460965 294620 324902 358771 Local timer interrupts
RES: 30111 286150 113295 268387 Rescheduling interrupts
CAL: 1140 1143 52 34 Function call interrupts
TLB: 2223 952 1184 2573 TLB shootdowns
SPU: 0 0 0 0 Spurious interrupts
ERR: 0
MIS: 0
--
Michael "Tired" Riepe <michael.riepe@...glemail.com>
X-Tired: Each morning I get up I die a little
--
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