From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] how can i choose HTB's prio
Date: Tue, 08 Oct 2002 14:19:22 +0000 [thread overview]
Message-ID: <marc-lartc-103408687820680@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103404484123694@msgid-missing>
On Tuesday 08 October 2002 04:06, hanhbnetfilter wrote:
> HTB and imq was used to control traffic.
> AC="tc class add dev eth0 parent"
> $AC 1: classid 1:1 htb rate 100kbps burst 2k
> $AC 1:2 classid 1:10 htb rate 50kbps ceil 100kbps
> burst 2k prio 1
> $AC 1:2 classid 1:11 htb rate 50kbps ceil 100kbps
> burst 2k prio 2
> $AC 1:2 classid 1:12 htb rate 50kbps ceil 100kbps
> burst 2k
> please tell me if i do not set prio, what is the
> default prio? low delay class can use prio 2,the
> others should use which prio?
prio is only used when all classes are served and there is some bandwidth
left. So if you have 20kbps in each class, you have 40kbs left. It will be
given to the class with the lowest prio.
But there is more going on. You can find more info on the homepage of htb (
http://luxik.cdi.cz/~devik/qos/htb/manual/userg.htm#prio). If you have a
class with the lowest prio and this class is not overlimit (it never wants to
send more traffic then the rate), it will get very low delays. BUT if you
send more traffic then the rate, the delays will increase.
I still have to figure out if you can use this to get low delays.
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/
prev parent reply other threads:[~2002-10-08 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 2:06 [LARTC] how can i choose HTB's prio hanhbnetfilter
2002-10-08 14:19 ` Stef Coene [this message]
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-103408687820680@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.