From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] various questions about tc & htb
Date: Thu, 28 Nov 2002 17:22:45 +0000 [thread overview]
Message-ID: <marc-lartc-103850422905287@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103849092823505@msgid-missing>
> You don't have to, but HTB assumes a mtu of 1600 by default which is
>
> a) wrong in most cases
> b) not always the same (e.g. loopback default is 16436)
>
> ------------< snip <------< snip <------< snip <------------
> root@oasis:~# tc class add dev eth0 parent 1:1 htb help
> Usage: ... qdisc add ... htb [default N] [r2q N]
> default minor id of class to which unclassified packets are sent {0}
> r2q DRR quantums are computed as rate in Bps/r2q {10}
> debug string of 16 numbers each 0-3 {0}
>
> ... class add ... htb rate R1 burst B1 [prio P] [slot S] [pslot PS]
> [ceil R2] [cburst B2] [mtu MTU] [quantum Q]
> rate rate allocated to this class (class can still borrow)
> burst max bytes burst which can be accumulated during idle period
> {computed}
> ceil definite upper class rate (no borrows) {rate}
> cburst burst but for ceil {computed}
> mtu max packet size we create rate map for {1600}
> prio priority of leaf; lower are served first {0}
> quantum how much bytes to serve from leaf at once {use r2q}
>
> TC HTB version 3.3
> root@oasis:~#
> ------------< snip <------< snip <------< snip <------------
>
> See, mtu = 1600 by default.
I did a quick search in the source of iproute2 and kernel, and as for as I can
see is mtu used to calculate the minimal burst :
/* compute minimal allowed burst from rate; mtu is added here to make
sute that buffer is larger than mtu and to have some safeguard
space */
if (!buffer) buffer = opt.rate.rate / HZ + mtu;
if (!cbuffer) cbuffer = opt.ceil.rate / HZ + mtu;
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-11-28 17:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 13:40 [LARTC] various questions about tc & htb Abraham van der Merwe
2002-11-28 15:56 ` Stef Coene
2002-11-28 16:45 ` Abraham van der Merwe
2002-11-28 17:18 ` Stef Coene
2002-11-28 17:22 ` Stef Coene [this message]
2002-11-28 17:59 ` Abraham van der Merwe
2002-11-29 12:56 ` Mathieu Deziel
2002-11-29 13:25 ` Mathieu Deziel
2002-11-29 17:11 ` Stef Coene
2002-11-29 17:17 ` Stef Coene
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=marc-lartc-103850422905287@msgid-missing \
--to=stef.coene@docum.org \
--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.