From: David Miller <davem@davemloft.net>
To: yangyingliang@huawei.com
Cc: fubar@us.ibm.com, andy@greyhouse.net, netdev@vger.kernel.org
Subject: Re: [PATCH] bonding: set correct tx_queue_len for bond_dev
Date: Tue, 30 Jul 2013 00:34:03 -0700 (PDT) [thread overview]
Message-ID: <20130730.003403.299786235452826263.davem@davemloft.net> (raw)
In-Reply-To: <51F7694A.1060703@huawei.com>
From: Yang Yingliang <yangyingliang@huawei.com>
Date: Tue, 30 Jul 2013 15:20:42 +0800
> With htb, sch->limit is set from bond_dev->tx_queue_len which
> is initialized to 0 in bond_setup.
This is intentional, software devices should not queue TX
packets.
You can only use the packet scheduler with hardware devices.
next prev parent reply other threads:[~2013-07-30 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 7:20 [PATCH] bonding: set correct tx_queue_len for bond_dev Yang Yingliang
2013-07-30 7:34 ` David Miller [this message]
2013-07-30 9:24 ` Yang Yingliang
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=20130730.003403.299786235452826263.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=yangyingliang@huawei.com \
/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).