From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Using HTB as an ISP "provisioning engine"
Date: Mon, 23 Dec 2002 16:53:36 +0000 [thread overview]
Message-ID: <marc-lartc-104066248227873@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104033114505084@msgid-missing>
On Monday 23 December 2002 17:30, raptor wrote:
> |Example :
> |You selled 1.1 Mbps to customer1 and 0.37 (=2.2Mbps/6) to 3 other
> | customers. So you have a total bandwidth of 2.2Mbps. But you have only
> | 1.2 Mbps available.
> |class rate = ceil = 1.2 Mbps
> | class1 rate = 0.6, ceil = 1.1Mbps
> | class2 rate = 0.2, ceil = 0.37Mbps
> | class3 rate = 0.2, ceil = 0.37Mbps
> | class4 rate = 0.2, ceil = 0.37Mbps
>
> ]- this is fasable only if u have predetermined number of clients, what if
> u have varing number of clients... any time u add or remove client u have
> to recalculate rate and ceil's... Yes u can achieve this with a little bit
> of scripting i.e. preprocessing the config but this is not a good
> solution.. If there was available some simple arithmetic in the QoS it
> would be better :")
Checking the parent rate/ceil will eat a lot of CPU cycles. That's why HTB is
ignoring the parent rate/ceil. It can be done, but it will be bad for
performance.
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-12-23 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 20:51 [LARTC] Using HTB as an ISP "provisioning engine" Brian Capouch
2002-12-19 21:10 ` Stef Coene
2002-12-20 5:24 ` S Mohan
2002-12-20 11:07 ` Daniel Egger
2002-12-23 16:30 ` raptor
2002-12-23 16:53 ` 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-104066248227873@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.