From: Stephen Hemminger <shemminger@vyatta.com>
To: Peter Lieven <pl@dlh.net>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: RFS seems to have incompatiblities with bridged vlans
Date: Mon, 7 Jun 2010 14:59:10 -0700 [thread overview]
Message-ID: <20100607145910.2458ac87@nehalam> (raw)
In-Reply-To: <62C40338-045A-417E-9B90-E59A320E1343@dlh.net>
On Mon, 7 Jun 2010 22:36:11 +0200
Peter Lieven <pl@dlh.net> wrote:
> Hi,
>
> i today tried out 2.6.32-rc2 and I see a lot of warning messages like this:
>
> Jun 7 22:33:15 172.21.55.20 kernel: [ 3012.575884] br141 received packet on queue 4, but number of RX queues is 1
>
> The host is a SMP system with 8 cores, so I think there is expected to be one rx queue per CPU, but it seems
> the bridge iface has only one.
>
The bridge interface has no queues. It doesn't queue any packets.
The test in receive packet path is not appropriate in this case.
Not sure what the right fix is. Pretending the bridge device has
multiple queues (num_queues == NUM_CPUS) is a possibility but
seems like overhead without real increase in parallelism.
next prev parent reply other threads:[~2010-06-07 21:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 20:36 RFS seems to have incompatiblities with bridged vlans Peter Lieven
2010-06-07 21:59 ` Stephen Hemminger [this message]
2010-06-07 22:19 ` Eric Dumazet
2010-06-07 22:30 ` John Fastabend
2010-06-07 23:13 ` John Fastabend
2010-06-08 14:18 ` Eric Dumazet
2010-06-08 23:00 ` Tom Herbert
2010-06-08 23:58 ` Tim Gardner
2010-06-09 1:08 ` John Fastabend
2010-06-09 1:52 ` Tom Herbert
2010-06-09 4:42 ` Eric Dumazet
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=20100607145910.2458ac87@nehalam \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=pl@dlh.net \
/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).