mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harald Hannelius <harald@iki.fi>
To: Michael Chan <mchan@broadcom.com>
Cc: Jiri Kosina <jkosina@suse.cz>, David Miller <davem@davemloft.net>,
	linux-kernel@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: Re: tg3 bad performance, lots of hardware interrupts
Date: Fri, 28 Mar 2008 20:09:17 +0200 (EET)	[thread overview]
Message-ID: <alpine.DEB.1.00.0803282006530.7191@penti.org> (raw)
In-Reply-To: <1206731211.6866.13.camel@dell>


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

  reply	other threads:[~2008-03-28 18:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-27 13:53 Harald Hannelius
2008-03-27 21:49 ` David Miller
2008-03-28  1:01   ` Michael Chan
2008-03-28 13:04     ` Harald Hannelius
2008-03-28 17:49       ` Michael Chan
2008-03-28 17:12         ` Jiri Kosina
2008-03-28 17:37           ` Harald Hannelius
2008-03-28 19:06             ` Michael Chan
2008-03-28 18:09               ` Harald Hannelius [this message]
2008-04-02  8:55             ` Harald Hannelius
2008-03-28 17:31         ` Harald Hannelius

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=alpine.DEB.1.00.0803282006530.7191@penti.org \
    --to=harald@iki.fi \
    --cc=davem@davemloft.net \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchan@broadcom.com \
    --cc=netdev@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

all inboxes | Powered by JetHome®