From: Denys Fedoryshchenko <nuclearcat@nuclearcat.com>
To: Netdev <netdev@vger.kernel.org>
Subject: HTB, HFSC, PIE, FIFO stuck on 2.4Gbit on default values
Date: Tue, 03 Nov 2015 19:33:22 +0200 [thread overview]
Message-ID: <14bd7629199800f798c8ab932e0285d3@visp.net.lb> (raw)
Hi
Recently i was testing shaping over single 10G cards, for speeds up to
3-4Gbps, and noticed interesting effect.
Shaping scheme:
Incoming bandwidth comes to switch port, with access vlan 100
Outgoing bandwidth leaves switch port with access vlan 200
Linux with Intel X710 connected to trunk port, bridge created, eth0.100
bridged to eth0.200
gso/gro/tso disabled (they doesn't work nice with shapers)
Sure latest kernel
Shaper are installed on eth0.200, and seems multiqueue works on eth0 in
general (i see packets are distributed over each queue), CPU load is
very low (max 20% on core, but usually below 5%).
I tried:
HTB with fq, pfifo, pie qdisc
HFSC with fq, pfifo, pie qdisc
After i run shaper with default values, i can see traffic start to queue
in classes and total traffic doesn't reach more than 2.4Gbit, and if i
remove shaper it directly reach 4Gbit.
The only trick i found, it is running pie with burst 10000 cburst 10000
in leaf classes, and 100000 in root class (i think 10000 in root class
might work as well). If i change discipline to fq, i am returning back
to 2.4Gbit, but it might be just because fq is not intended to be used
with HTB leaf class.
So in my case burst/cburst solved issue, but i suspect maybe possible
more elegant solution/tuning, than putting some random values?
Is there any particular reason why i am limited by ~2.4Gbit on any other
settings?
next reply other threads:[~2015-11-03 17:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 17:33 Denys Fedoryshchenko [this message]
2015-11-03 19:11 ` HTB, HFSC, PIE, FIFO stuck on 2.4Gbit on default values Eric Dumazet
2015-11-03 19:17 ` Denys Fedoryshchenko
2015-11-03 19:49 ` Eric Dumazet
2015-11-03 20:01 ` David Miller
2015-11-03 20:24 ` Denys Fedoryshchenko
2015-11-03 21:23 ` Eric Dumazet
2015-11-04 4:12 ` Denys Fedoryshchenko
2015-11-04 4:28 ` Eric Dumazet
2015-11-04 4:49 ` Denys Fedoryshchenko
2015-11-04 5:02 ` Eric Dumazet
2015-11-03 21:04 ` Andrew
2015-11-03 22:02 ` Eric Dumazet
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=14bd7629199800f798c8ab932e0285d3@visp.net.lb \
--to=nuclearcat@nuclearcat.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).