From: Andy Gospodarek <andy@greyhouse.net>
To: netdev@vger.kernel.org, Phil Oester <kernel@linuxace.com>
Cc: Ben Hutchings <bhutchings@solarflare.com>,
Jay Vosburgh <fubar@us.ibm.com>
Subject: [PATCH 1/2] bonding: fix incorrect transmit queue offset
Date: Wed, 23 Feb 2011 14:42:49 -0500 [thread overview]
Message-ID: <1298490169-5224-1-git-send-email-andy@greyhouse.net> (raw)
Users noticed the following messages:
kernel: bond0 selects TX queue 16, but real number of TX queues is 16
were filling their logs when frames received from a device that
contained 16 input queues were being forwarded out of a bonded device.
Ben pointed out that the contents of skb->queue_mapping cannot be
directly mapped to a transmit queue, so I went with his suggestion for a
solution to the offset problem.
The function now also warns the user to increase the default value for
tx_queues if needed and returns a valid tx queue to dev_pick_tx.
Signed-off-by: Andy Gospodarek <andy@greyhouse.net>
Reported-by: Phil Oester <kernel@linuxace.com>
CC: Ben Hutchings <bhutchings@solarflare.com>
---
drivers/net/bonding/bond_main.c | 24 +++++++++++++++++-------
1 files changed, 17 insertions(+), 7 deletions(-)
diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
index 77e3c6a..1512c83 100644
--- a/drivers/net/bonding/bond_main.c
+++ b/drivers/net/bonding/bond_main.c
@@ -4533,15 +4533,25 @@ out:
return res;
}
+/*
+ * This helper function exists to help dev_pick_tx get the correct
+ * destination queue. Using a helper function skips the a call to
+ * skb_tx_hash and will put the skbs in the queue we expect on their
+ * way down to the bonding driver.
+ */
static u16 bond_select_queue(struct net_device *dev, struct sk_buff *skb)
{
- /*
- * This helper function exists to help dev_pick_tx get the correct
- * destination queue. Using a helper function skips the a call to
- * skb_tx_hash and will put the skbs in the queue we expect on their
- * way down to the bonding driver.
- */
- return skb->queue_mapping;
+ u16 txq = skb_rx_queue_recorded(skb) ? skb_get_rx_queue(skb) : 0;
+
+ while (txq >= dev->real_num_tx_queues) {
+ /* let the user know if we do not have enough tx queues */
+ if (net_ratelimit())
+ pr_warning("%s selects invalid tx queue %d. Consider"
+ " setting module option tx_queues > %d.",
+ dev->name, txq, dev->real_num_tx_queues);
+ txq -= dev->real_num_tx_queues;
+ }
+ return txq;
}
static netdev_tx_t bond_start_xmit(struct sk_buff *skb, struct net_device *dev)
--
1.7.4
next reply other threads:[~2011-02-23 19:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 19:42 Andy Gospodarek [this message]
2011-02-23 22:19 ` [PATCH 1/2] bonding: fix incorrect transmit queue offset Jay Vosburgh
2011-02-23 23:12 ` Andy Gospodarek
2011-02-23 23:08 ` Phil Oester
2011-02-23 23:13 ` David Miller
2011-02-23 23:37 ` Ben Hutchings
2011-02-23 23:43 ` Andy Gospodarek
2011-02-23 23:54 ` David Miller
2011-02-25 22:56 ` Phil Oester
2011-03-01 15:31 ` [PATCH 1/2 net-next][v2] " Andy Gospodarek
2011-03-02 1:40 ` Phil Oester
2011-03-04 17:37 ` Jay Vosburgh
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=1298490169-5224-1-git-send-email-andy@greyhouse.net \
--to=andy@greyhouse.net \
--cc=bhutchings@solarflare.com \
--cc=fubar@us.ibm.com \
--cc=kernel@linuxace.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).