All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] 64 commited / 128 burstable peak service
Date: Mon, 01 Sep 2003 17:44:08 +0000	[thread overview]
Message-ID: <marc-lartc-106243843216241@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106241021421908@msgid-missing>

On Monday 01 September 2003 11:55, Damjan wrote:
> I would like to give my customers a special 64/128 service.
> With this service you can:
>  - download at 64kbit/s all you like (unless...)
>  - you can have peaks up to 128kbit/s, but the peaks should not be longer
>  than (say) 5 minutes, and then, after that you will have to wait your
>  bucket to replenish in order to get the 64 commited rate.
>
> The point is the average should never be above 64kbits, burstable peaks
> are allowed for some time, but it hurts your service.
>
>
> I plan to implement this using HTB, since I'll have several customers,
> on one router, that will have this service...
>
> Can this be done?
> What parameters should I look for when setting HTB?
You can only do this with external monitoring and scripting.  You can set some 
burst parameters with htb, but they are only for small burst.  Not for big 
bursts like you want to do.

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/

  reply	other threads:[~2003-09-01 17:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-01  9:55 [LARTC] 64 commited / 128 burstable peak service Damjan
2003-09-01 17:44 ` Stef Coene [this message]
2003-09-01 20:08 ` Damjan

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-106243843216241@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.