From: Phil Oester <kernel@linuxace.com>
To: Andy Gospodarek <andy@greyhouse.net>
Cc: netdev@vger.kernel.org, Ben Hutchings <bhutchings@solarflare.com>,
Jay Vosburgh <fubar@us.ibm.com>
Subject: Re: [PATCH net-next-2.6] bonding: fix user-controlled queuing issues
Date: Tue, 22 Feb 2011 08:48:36 -0800 [thread overview]
Message-ID: <20110222164836.GA15040@linuxace.com> (raw)
In-Reply-To: <20110222161941.GE11864@gospo.rdu.redhat.com>
On Tue, Feb 22, 2011 at 11:19:41AM -0500, Andy Gospodarek wrote:
> Phil,
>
> Can you send me the minimal set of tc rules that selects output queue 16
> and the output of /proc/net/bonding/bond0?
>
> Private email is fine if you do not want to post it to the list.
>
> Thanks,
>
> -andy
I have no tc rules which select output queue 16 (I have no tc rules at all
in fact).
Output of /proc/net/bonding/bond0 below. The bond consists of two Intel
igb nics, which only have 8 queues. Note, however, that eth0 is an ixgbe,
which has 16 queues:
ixgbe 0000:0b:00.0: Multiqueue Enabled: Rx Queue count = 16, Tx Queue count = 16
which may answer your question as to what is selecting queue 16.
Phil
Ethernet Channel Bonding Driver: v3.7.0 (June 2, 2010)
Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2+3 (2)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
802.3ad info
LACP rate: slow
Aggregator selection policy (ad_select): stable
Active Aggregator Info:
Aggregator ID: 1
Number of ports: 2
Actor Key: 17
Partner Key: 6
Partner Mac Address: 00:d0:05:xx:xx:xx
Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:1b:21:xx:xx:xx
Aggregator ID: 1
Slave Interface: eth2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:1b:21:xx:xx:xx
Aggregator ID: 1
next prev parent reply other threads:[~2011-02-22 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 22:53 [PATCH net-next-2.6] bonding: fix user-controlled queuing issues Andy Gospodarek
2011-02-22 15:55 ` Phil Oester
2011-02-22 16:19 ` Andy Gospodarek
2011-02-22 16:48 ` Phil Oester [this message]
2011-02-22 21:24 ` Andy Gospodarek
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=20110222164836.GA15040@linuxace.com \
--to=kernel@linuxace.com \
--cc=andy@greyhouse.net \
--cc=bhutchings@solarflare.com \
--cc=fubar@us.ibm.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).