From: Jason Tackaberry <tack@auc.ca>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb guarantee bandwidth
Date: Fri, 30 Aug 2002 20:35:44 +0000 [thread overview]
Message-ID: <marc-lartc-103073957309899@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103060557613880@msgid-missing>
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.
Doesn't that work out? Of course it's entirely academic, since it's not
as if adding one extra rule makes it more complicated or less efficient
in practice.
Jason.
--
Academic Computing Support Specialist
Algoma University College
Sault Ste. Marie, Ontario
705-949-2301 x330 Personal Home Page
http://www.auc.ca http://sault.org
_______________________________________________
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-30 20:35 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
2002-08-30 20:35 ` Jason Tackaberry [this message]
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-103073957309899@msgid-missing \
--to=tack@auc.ca \
--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.