From: "Michael Chan" <mchan@broadcom.com>
To: "Christophe Ngo Van Duc" <cngovanduc@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: bnx2/5709: Strange interrupts spread
Date: Fri, 2 Jul 2010 13:58:31 -0700 [thread overview]
Message-ID: <1278104311.11828.12.camel@HP1> (raw)
In-Reply-To: <AANLkTiniNNPV9ztxXHtX4np7PIZabkm0I4v5O29chf8i@mail.gmail.com>
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.
next prev parent reply other threads:[~2010-07-02 20:59 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 [this message]
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
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=1278104311.11828.12.camel@HP1 \
--to=mchan@broadcom.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.