From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb guarantee bandwidth
Date: Thu, 29 Aug 2002 12:53:44 +0000 [thread overview]
Message-ID: <marc-lartc-103062573831171@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103060557613880@msgid-missing>
On Thursday 29 August 2002 10:53, Ciprian Niculescu wrote:
> hi,
>
> you give to all the clients all the bandwith or limited at 64k, but with
> different priorities.
>
> class parent 1: classid 1:5 htb rate 128kbit
> class parent 1:5 classid 1:1 htb rate 64kbit ceil 128kbit prio 1
> class parent 1:5 classid 1:2 htb rate 64kbit ceil 128kbit prio 2
>
> you put the client that you want to have guaranted 64kbps in 1:1, and
> the other two in 1:2.
The prio is only used to split the traffic that's available after the rates
are satisfied. In this case, the prio will change nothing. But if you have
3 classes like :
class parent 1: classid 1:5 htb rate 128kbit
class parent 1:5 classid 1:1 htb rate 32kbit ceil 128kbit prio 1
class parent 1:5 classid 1:2 htb rate 32kbit ceil 128kbit prio 1
class parent 1:5 classid 1:3 htb rate 64kbit ceil 128kbit prio 2
and class 1:1 uses no bandwidth. Class 1:2 will get 32kbit, class 1:3 64kbit,
so 32 kbit left. Class 1:2 has the lowest prio, so it will get the remaining
32kbit. So each class gets 64 kbit.
The rate for a class is always guaranteed. So you don't need an isolated
option like in cbq.
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-08-29 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 7:31 [LARTC] htb guarantee bandwidth Rohan Almeida
2002-08-29 8:53 ` Ciprian Niculescu
2002-08-29 12:53 ` Stef Coene [this message]
2002-08-30 20:35 ` Jason Tackaberry
2002-08-30 20:44 ` 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-103062573831171@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.