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: <AANLkTillLjztYe7mmyO_LoTXavDtTd2nsaAsd22z0dG-@mail.gmail.com>
Date:	Sun, 4 Jul 2010 17:36:40 -0300
From:	Christophe Ngo Van Duc <cngovanduc@...il.com>
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: bnx2/5709: Strange interrupts spread

Is it a requirement that the interface has an IP address for the TX
and RX hash to work?

Christophe.

On Fri, Jul 2, 2010 at 7:12 PM, Christophe Ngo Van Duc
<cngovanduc@...il.com> wrote:
> Hi
>
> Well that's the strange thing: it is IP traffic. The only difference
> with eth0 and eth1 is that eth2 and eth3 belongs to a bridge (br0).
>
> Best Regards,
> Christophe.
>
> On 7/2/10, Michael Chan <mchan@...adcom.com> wrote:
>>
>> 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.
>>
>>
>>
>
> --
> Sent from my mobile device
>
--
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