From: Yang Yingliang <yangyingliang@huawei.com>
To: Jay Vosburgh <fubar@us.ibm.com>,
Andy Gospodarek <andy@greyhouse.net>,
"David S. Miller" <davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: [PATCH] bonding: set correct tx_queue_len for bond_dev
Date: Tue, 30 Jul 2013 15:20:42 +0800 [thread overview]
Message-ID: <51F7694A.1060703@huawei.com> (raw)
When we set bandwidth on bond_dev with htb, it's not precise.
Because the length of skb_buff queue is bigger than sch->limit
whose value is 0, some packets are dropped.
This leads to bond device can't make full use of the bandwidth
and influence the accuracy.
With htb, sch->limit is set from bond_dev->tx_queue_len which
is initialized to 0 in bond_setup.
To fix this issue, set the bond_dev's tx_queue_len to slave_dev's.
Example:
tc qdisc add dev bond0 root handle 1: htb default 1
tc class add dev bond0 parent 1:0 classid 1:1 htb rate 1Gbit ceil 1Gbit
iperf -c host -t 30 -i 10
With old bonding:
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 579 MBytes 486 Mbits/sec
[ 3] 10.0-20.0 sec 604 MBytes 507 Mbits/sec
[ 3] 20.0-30.0 sec 551 MBytes 462 Mbits/sec
[ 3] 0.0-30.0 sec 1.69 GBytes 485 Mbits/sec
With new bonding:
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 1.11 GBytes 955 Mbits/sec
[ 3] 10.0-20.0 sec 1.11 GBytes 955 Mbits/sec
[ 3] 20.0-30.0 sec 1.11 GBytes 955 Mbits/sec
[ 3] 0.0-30.0 sec 3.33 GBytes 955 Mbits/sec
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
---
drivers/net/bonding/bond_main.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
index dbbea0e..2536426 100644
--- a/drivers/net/bonding/bond_main.c
+++ b/drivers/net/bonding/bond_main.c
@@ -1860,6 +1860,12 @@ int bond_enslave(struct net_device *bond_dev, struct net_device *slave_dev)
goto err_dest_symlinks;
}
+ if (!bond_dev->tx_queue_len)
+ bond_dev->tx_queue_len = slave_dev->tx_queue_len;
+ else
+ bond_dev->tx_queue_len = min(slave_dev->tx_queue_len,
+ bond_dev->tx_queue_len);
+
pr_info("%s: enslaving %s as a%s interface with a%s link.\n",
bond_dev->name, slave_dev->name,
bond_is_active_slave(new_slave) ? "n active" : " backup",
--
1.7.12
.
next reply other threads:[~2013-07-30 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 7:20 Yang Yingliang [this message]
2013-07-30 7:34 ` [PATCH] bonding: set correct tx_queue_len for bond_dev David Miller
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=51F7694A.1060703@huawei.com \
--to=yangyingliang@huawei.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--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).