Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Daniel Egger <egger@spotnic.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Using HTB as an ISP "provisioning engine"
Date: Fri, 20 Dec 2002 11:07:08 +0000	[thread overview]
Message-ID: <marc-lartc-104038240606180@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104033114505084@msgid-missing>

Am Don, 2002-12-19 um 22.10 schrieb Stef Coene:

> 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

> The bandwidth you selled to the customers is the ceil.  They never can use 
> more then the ceil.  If one customer is using no bandwidth, the remaining 
> bandwidth is given to the other customers.
> If all customers are using all bandwidth, each customer is "punished" in the 
> same way.

Nice, however (see other mail) it seems unpossible to remove subclasses
on-the-fly which is a hard requirement here. Do I have to recreate the
whole tree on the fly? If so, won't this negatively affect the queues
because all statistics are lost?

-- 
Servus,
       Daniel


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2002-12-20 11:07 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 [this message]
2002-12-23 16:30 ` raptor
2002-12-23 16:53 ` 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-104038240606180@msgid-missing \
    --to=egger@spotnic.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox