netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eldon Koyle <esk-netdev@esk.cs.usu.edu>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: ixgbe RSS not working as expected with 8021q and bridging
Date: Tue, 15 Dec 2009 10:21:19 -0700	[thread overview]
Message-ID: <20091215172119.GF20231@esk.cs.usu.edu> (raw)
In-Reply-To: <4B218E36.4030808@gmail.com>

On  Dec 11  1:11+0100, Eric Dumazet wrote:
> Le 11/12/2009 00:11, Eldon Koyle a écrit :
> > We have built a firewall with two 10 Gbit interfaces (intel 82598EB) and
> > are doing some testing.  A simple bridge between the two interfaces acts
> > as expected with packets being distributed fairly evenly across all of
> > the rx/tx queues.
> > 
> > We then switched to tagged vlans on both interfaces (10 vlans each, 8
> > source and 8 dest addresses per vlan) and bridged eth0.N to eth1.N, and
> > many of our queues (and CPUs) remained idle, and all of our VLAN traffic
> > went out on the same tx queue.  Are multiple transmit queues supported
> > with 802.1q?  How do we figure out what is causing some of our receive
> > queues to be unused?
> > 
> > We are using 2.6.31 (from Debian) and ixgbe-2.0.44.14 .
> > 
> 
> You need more recent kernel (2.6.32) to get multi queue support on vlans, sorry.

Excellent.  2.6.32 solved half of the problem.  Now, we are using the
same number of rx and tx queues.  We are still seeing no packets on 3 of
our 8 rx queues on each interface, though (no packets on 2, 4 or 6).
Does the card assign queues in hardware, or is that handled by the
kernel?

-- 
Eldon Koyle

  reply	other threads:[~2009-12-15 17:21 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 [this message]
2009-12-15 19:33     ` Eric Dumazet
2010-02-10 20:50       ` Eldon Koyle
2010-02-12 19:03         ` Eldon Koyle
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=20091215172119.GF20231@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).