From: Tim Gardner <tim.gardner@canonical.com>
To: netdev <netdev@vger.kernel.org>
Subject: 2.6.35-rc2, CONFIG_RPS is filling the dmesg log
Date: Tue, 08 Jun 2010 14:55:26 -0600 [thread overview]
Message-ID: <4C0EAE3E.4070708@canonical.com> (raw)
With 2.6.35-rc2 my dmesg log is being flooded with messages like this:
br0 received packet on queue 4, but number of RX queues is 1
This machine is bridged for KVM and has 2 igb network adapters.
The root cause appears to be CONFIG_RPS=y and the fact that none of the
drivers that call skb_record_rx_queue() perform their net device
allocation using alloc_netdev_mq(), thereby initializing num_rx_queues
to a maximum of 1.
Given that this is early RPS days, is the warning in get_rps_cpu()
really necessary? It would appear that _all_ of the multi-receive queue
devices that call skb_record_rx_queue() will cause this log noise.
By the way, how do you turn off CONFIG_RPS? The only way I could get it
disabled was to change the default in net/Kconfig to 'n'.
rtg
--
Tim Gardner tim.gardner@canonical.com
next reply other threads:[~2010-06-08 21:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 20:55 Tim Gardner [this message]
2010-06-09 13:27 ` 2.6.35-rc2, CONFIG_RPS is filling the dmesg log Tim Gardner
2010-06-09 13:42 ` Eric Dumazet
2010-06-09 15:22 ` Tim Gardner
2010-06-09 15:27 ` 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=4C0EAE3E.4070708@canonical.com \
--to=tim.gardner@canonical.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.