Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757410AbYC1SJi (ORCPT ); Fri, 28 Mar 2008 14:09:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755404AbYC1SJ2 (ORCPT ); Fri, 28 Mar 2008 14:09:28 -0400 Received: from penti.org ([193.167.33.200]:53577 "EHLO penti.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755052AbYC1SJ1 (ORCPT ); Fri, 28 Mar 2008 14:09:27 -0400 Date: Fri, 28 Mar 2008 20:09:17 +0200 (EET) From: Harald Hannelius X-X-Sender: harald@penti.org To: Michael Chan cc: Jiri Kosina , David Miller , linux-kernel@vger.kernel.org, netdev Subject: Re: tg3 bad performance, lots of hardware interrupts In-Reply-To: <1206731211.6866.13.camel@dell> Message-ID: References: <20080327.144925.196529669.davem@davemloft.net> <1206666100.5368.6.camel@dell> <1206726560.6866.5.camel@dell> <1206731211.6866.13.camel@dell> User-Agent: Alpine 1.00 (DEB 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2321 Lines: 51 On Fri, 28 Mar 2008, Michael Chan wrote: > On Fri, 2008-03-28 at 19:37 +0200, Harald Hannelius wrote: >> # cat /proc/interrupts >> CPU0 CPU1 >> 0: 111 1 IO-APIC-edge timer >> 1: 0 2 IO-APIC-edge i8042 >> 2: 0 0 XT-PIC-XT cascade >> 5: 0 0 IO-APIC-fasteoi sata_nv >> 7: 856 51 IO-APIC-fasteoi ohci_hcd:usb2 >> 10: 0 3 IO-APIC-fasteoi sata_nv, ehci_hcd:usb1 >> 11: 4305 7 IO-APIC-fasteoi sata_nv >> 12: 0 4 IO-APIC-edge i8042 >> 216: 4217 128932 PCI-MSI-edge eth2 >> 217: 161107 685351 PCI-MSI-edge eth0 >> NMI: 0 0 Non-maskable interrupts >> LOC: 2380762 2619917 Local timer interrupts >> RES: 3000 3269 Rescheduling interrupts >> CAL: 16 31 function call interrupts >> TLB: 64 111 TLB shootdowns >> TRM: 0 0 Thermal event interrupts >> SPU: 0 0 Spurious interrupts >> ERR: 1 >> MIS: 0 >> >> Well, shared or not, yes and no. I think that /proc/interrupts >> contains >> soft-interrupts. The problem child is interface eth2. >> >> As rapported by ifconfig the interface is on IRQ 5: > > eth2 is using MSI. When using MSI, the IRQ reported by ifconfig is not > accurate. You said you have tried booting with nomsi, but have you > confirmed that by checking /proc/interrupts? I did, at least the interface wasn't on MSI-edge anymore. I cannot remember what IRQ the NIC took when booted with pci=nomsi (something like that), it could have been 10 or other IRQ below 20, if I recall correctly. -- A: Top Posters! | s/y Charlotta | Q: What is the most annoying thing on mailing lists? | FIN-2674 | http://www.fe83.org/ Finn Express Purjehtijat ry | ============= | Harald H Hannelius | harald (At) iki (dot) fi | GSM +358 50 594 1020 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/