netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Ngo Van Duc <cngovanduc@gmail.com>
To: netdev@vger.kernel.org
Subject: Re: bnx2/5709: Strange interrupts spread
Date: Mon, 19 Jul 2010 12:55:57 -0300	[thread overview]
Message-ID: <AANLkTikfEED5Hvt80G6EnMwPBByMuw4r1Xg2ITjuZ0eV@mail.gmail.com> (raw)
In-Reply-To: <AANLkTiniNNPV9ztxXHtX4np7PIZabkm0I4v5O29chf8i@mail.gmail.com>

Dear list,

So i've been able to do some test today:
If I put the 2 interface in a bridge with no IP adress, the interrupts
are on 1 CPU
If I put the 2 interface in a bridge with IP adress, the interrupts
are still on 1 CPU
If I put the 2 interface outside the bridge with IP address,
everything works fine the interrupts get spread on the CPU

So the conclusion seems to be that when the bnx2 is put into
promiscuous mode by the bridge, the RSS hash stop to work even if
traffic is IP in nature.

Best regards,
Christophe.

On Fri, Jul 2, 2010 at 5:33 PM, Christophe Ngo Van Duc
<cngovanduc@gmail.com> wrote:
> Dear list,
>
> I hope I am posting to the correct place...
>
> I am facing a strange issue on a HP DL 360.
>
> I have 2 internal ethernet cards (the one that came by default with
> the server) and 2 additional ethernet cards for a total for 4 ethernet
> cards.
>
> The 2 internal cards are running fine as of interrupts (for example eth1):
>           CPU0       CPU1       CPU2       CPU3       CPU4       CPU5
>      CPU6       CPU7
>
>  71:        604      11933         40       1537          0
> 0          0       6043   PCI-MSI-edge      eth1-0
>  72:      24805       9795       3606          0        128
> 0       3365          0   PCI-MSI-edge      eth1-1
>  73:          0        279          0        429         38
> 16540          0      30843   PCI-MSI-edge      eth1-2
>  74:          0          0      25365        267          0
> 0         89      15541   PCI-MSI-edge      eth1-3
>  75:       7244      24108          0          0      16488
> 0        240          0   PCI-MSI-edge      eth1-4
>  76:      21378       3628       7726          0         49
> 247       2871          0   PCI-MSI-edge      eth1-5
>  77:          0          0      47199        459         13
> 46      63064         18   PCI-MSI-edge      eth1-6
>  78:          0       6230         67        283        259
> 82       7846      27130   PCI-MSI-edge      eth1-7
>
> 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   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
>
> If I understand correctly the RSS hash is used to dispatch the packets
> into the different queues running on the different CPU.
>
> Why then my internal cards are running fine but the additional cards
> (eth2 and eth3) are presenting this behavior where all interrupts goes
> to one CPU?
>
> Thanks for your help in understanding this. (see below for config details)
>
> Christophe.
>
> All are detected correctly at boot:
> Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.0.8e (April 13, 2010)
> bnx2 0000:02:00.0: PCI INT A -> GSI 31 (level, low) -> IRQ 31
> bnx2 0000:02:00.0: setting latency timer to 64
> eth0: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found
> at mem f4000000, IRQ 31, node addr f4:ce:46:86:a1:00
> bnx2 0000:02:00.1: PCI INT B -> GSI 39 (level, low) -> IRQ 39
> bnx2 0000:02:00.1: setting latency timer to 64
> eth1: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found
> at mem f2000000, IRQ 39, node addr f4:ce:46:86:a1:02
> bnx2 0000:07:00.0: PCI INT A -> GSI 24 (level, low) -> IRQ 24
> bnx2 0000:07:00.0: setting latency timer to 64
> eth2: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found
> at mem fa000000, IRQ 24, node addr 00:26:55:87:17:98
> bnx2 0000:07:00.1: PCI INT B -> GSI 34 (level, low) -> IRQ 34
> bnx2 0000:07:00.1: setting latency timer to 64
> eth3: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found
> at mem f8000000, IRQ 34, node addr 00:26:55:87:17:9a
>
> Kernel is 2.6.31-13
> Broadcom driver bnx2 v2.0.8e
>
> eth0 is a normal interface with an Ip address
> eth1 is a normal interface with an Ip address
> eth2 belongs to a bridge interface without an ip address, running tc (htb)
> eth3 belongs to the same bridge interface without an ip address
>

  parent reply	other threads:[~2010-07-19 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-02 20:33 bnx2/5709: Strange interrupts spread Christophe Ngo Van Duc
2010-07-02 20:58 ` Michael Chan
2010-07-02 22:12   ` Christophe Ngo Van Duc
2010-07-04 20:36     ` Christophe Ngo Van Duc
2010-07-05 22:56       ` Rick Jones
2010-07-08 20:06         ` Christophe Ngo Van Duc
2010-07-19 15:55 ` Christophe Ngo Van Duc [this message]
2010-07-19 18:47   ` Michael Chan
2010-07-19 19:47     ` Eric Dumazet
2010-07-19 20:29       ` Michael Chan

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=AANLkTikfEED5Hvt80G6EnMwPBByMuw4r1Xg2ITjuZ0eV@mail.gmail.com \
    --to=cngovanduc@gmail.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;
as well as URLs for NNTP newsgroup(s).