netdev - Re: bnx2/5709: Strange interrupts spread

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1278104311.11828.12.camel@HP1>
Date:	Fri, 2 Jul 2010 13:58:31 -0700
From:	"Michael Chan" <mchan@...adcom.com>
To:	"Christophe Ngo Van Duc" <cngovanduc@...il.com>
cc:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: bnx2/5709: Strange interrupts spread


On Fri, 2010-07-02 at 13:33 -0700, Christophe Ngo Van Duc wrote:
> On eth2 (external card) all interrupts goes to CPU0
>
>
>            CPU0       CPU1       CPU2       CPU3       CPU4       CPU5       CPU6       CPU7
>   80:   46973077          0          0          0          0          0          0          0   PCI-MSI-edge      eth2-0
>   81:          0          0          0          0          0          0          0          0   PCI-MSI-edge      eth2-1
>   82:          0          0          0          0          0          0          0          0   PCI-MSI-edge      eth2-2
>   83:          0          0          0          0          0          0          0          0   PCI-MSI-edge      eth2-3
>   84:          0          0          0          0          0          0          0          0   PCI-MSI-edge      eth2-4
>   85:          0          0          0          0          0          0          0          0   PCI-MSI-edge      eth2-5
>   86:          0          0       2445          0         37          0       8463         13   PCI-MSI-edge      eth2-6
>   87:          0          0          0          0          0          0          0          0   PCI-MSI-edge      eth2-7

Reformatted your output

> If I understand correctly the RSS hash is used to dispatch the packets
> into the different queues running on the different CPU.

It looks like most interrupts go to eth2-0, a few go to eth2-6.  The rx
ring for eth2-0 is for non-IP packets.  The RSS hash will hash IP
packets and place them on eth2-1 to eth2-7.  eth2-0 also handles tx
interrupts for TX ring 0.  TX traffic is hashed by the stack.

What kind of traffic is passing through eth2?

Thanks.


--
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