From: Eldon Koyle <esk-netdev@esk.cs.usu.edu>
To: netdev@vger.kernel.org
Cc: eric.dumazet@gmail.com
Subject: Re: ixgbe RSS not working as expected with 8021q and bridging
Date: Fri, 12 Feb 2010 12:03:40 -0700 [thread overview]
Message-ID: <20100212190340.GB20231@esk.cs.usu.edu> (raw)
In-Reply-To: <20100210205048.GT20231@esk.cs.usu.edu>
On Feb 10 13:50-0700, Eldon Koyle wrote:
<snip>
> I am now trying 2.6.32.7 with the in-tree ixgbe driver. I am still
> seeing some unusual behavior when bridging VLAN interfaces. It looks
> like there is an off-by-one error in the mapping from rx queue to tx
> queue (ie. packets are sent on <rx queue number>-1 instead of using the
> same rx and tx queue number).
>
> Any idea what might cause this?
Looking at the code, we are having difficulty finding the problem. I
think we did find an accounting error in the vlan code, though.
In net/8021q/vlan_dev.c:
static netdev_tx_t vlan_dev_hard_start_xmit(struct sk_buff *skb,
struct net_device *dev)
{
int i = skb_get_queue_mapping(skb);
struct netdev_queue *txq = netdev_get_tx_queue(dev, i);
...
if (likely(ret == NET_XMIT_SUCCESS)) {
txq->tx_packets++;
txq->tx_bytes += len;
} else
txq->tx_dropped++;
...
}
skb_get_queue_mapping returns skb->queue_mapping, which is rx_queue + 1
or 0 for unset.
Does dev->_tx[0] have some special meaning, or is this wrong?
--
Eldon Koyle
--
I have a theory that it's impossible to prove anything, but I can't prove it.
next prev parent reply other threads:[~2010-02-12 19:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 23:11 ixgbe RSS not working as expected with 8021q and bridging Eldon Koyle
2009-12-11 0:11 ` Eric Dumazet
2009-12-15 17:21 ` Eldon Koyle
2009-12-15 19:33 ` Eric Dumazet
2010-02-10 20:50 ` Eldon Koyle
2010-02-12 19:03 ` Eldon Koyle [this message]
2010-02-12 19:48 ` Eric Dumazet
2010-02-12 19:52 ` David Miller
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=20100212190340.GB20231@esk.cs.usu.edu \
--to=esk-netdev@esk.cs.usu.edu \
--cc=eric.dumazet@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 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).