On Friday 30 August 2002 22:35, Jason Tackaberry wrote:
> On Thu, 2002-08-29 at 08:53, Stef Coene wrote:
> > 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 :
>
> Yes, the prio will change nothing, so it might as well look like this:
>
> 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 1
>
> If we put the client with the guaranteed rate (call him A) into 1:1, and
> the other two clients (B and C) into 1:2, it should work out the same
> way. If A uses 64kbit, the remaining 64kbit is split between B and C,
> and assuming there is a fair qdisc attached to 1:2, they should each get
> 32kbit. If B is inactive, both A and C will get 64kbit: their classes'
> guaranteed rates. If A is inactive, 1:2 will hit the ceil and B and C
> will share 128kbit, so each gets 64kbit.
Better, attach 2 new classes to 1:2 :
class parent 1:2 classid 1:10 htb rate 16kbit ceil 128kbit prio 1
class parent 1:2 classid 1:20 htb rate 48kbit ceil 128kbit prio 1
Class 10 will get 25% of the available bandwidth of class 1:2 and class 20
75%.
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/
