From: Brian Rak <brak@gameservers.com>
To: lartc@vger.kernel.org
Subject: tc burst size rollover
Date: Tue, 11 Mar 2014 16:48:06 +0000 [thread overview]
Message-ID: <531F3E46.4050503@gameservers.com> (raw)
I'm seeing some weird behavior when I'm trying to add some htb queue
settings with large burst sizes. It seems that if I specify a burst
size over 3355443kb, the number rolls over. For example:
# tc class add dev vnet1 parent 1: classid 1:1 htb rate 12500kbps ceil
125000kbps burst 3355444kb
# tc class show dev vnet1 parent 1:
class htb 1:1 root prio 0 rate 100000Kbit ceil 1000Mbit burst 812b
cburst 1375b
Is there supposed to be a limitation here? I can't seem to find anything
in the documentation talking about it.
I've tested this with iproute2-3.12.0 on 3.13.1-1.el6.elrepo.x86_64.
This is the full set of commands I was using (these are what libvirt
applies by default):
tc qdisc del dev vnet1 root
tc qdisc del dev vnet1 ingress
tc qdisc add dev vnet1 root handle 1: htb default 1
tc class add dev vnet1 parent 1: classid 1:1 htb rate 12500kbps ceil
125000kbps burst 3355444kb
tc class show dev vnet1 parent 1:
Ultimately, I'm trying to allow bursts at 1000mbit up to 100GB or so,
then restrict things to a lower speed. I'm not aware of any way to do
this aside from using a large burst size.
reply other threads:[~2014-03-11 16:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=531F3E46.4050503@gameservers.com \
--to=brak@gameservers.com \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.