From: Eric Dumazet <eric.dumazet@gmail.com>
To: Michael Chan <mchan@broadcom.com>
Cc: Christophe Ngo Van Duc <cngovanduc@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: bnx2/5709: Strange interrupts spread
Date: Mon, 19 Jul 2010 21:47:55 +0200 [thread overview]
Message-ID: <1279568875.2458.0.camel@edumazet-laptop> (raw)
In-Reply-To: <1279565231.20559.14.camel@HP1>
Le lundi 19 juillet 2010 à 11:47 -0700, Michael Chan a écrit :
> On Mon, 2010-07-19 at 08:55 -0700, Christophe Ngo Van Duc wrote:
> > 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.
>
> I did a quick test with bridging and saw no problem with RSS. I did see
> this though:
>
> br0 received packet on queue 4, but number of RX queues is 1
>
> Looks like it is a warning message from RPS.
>
Christophe uses an old kernel, not RPS enabled ;)
next prev parent reply other threads:[~2010-07-19 19:48 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
2010-07-19 18:47 ` Michael Chan
2010-07-19 19:47 ` Eric Dumazet [this message]
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=1279568875.2458.0.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=cngovanduc@gmail.com \
--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