From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Thousands of classes, BW throttling and prioritizing??
Date: Sat, 05 Oct 2002 19:14:06 +0000 [thread overview]
Message-ID: <marc-lartc-103384534918589@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103372977201244@msgid-missing>
On Friday 04 October 2002 13:12, Dare wrote:
> Hello,
>
> I need to limit the bandwidth to 1Mbit per user IP (and never give more)
> and inside of each 1Mbit prioritize minimum-delay traffic (video stream
> from specific servers, so I mangle TOS for packets from those). The
> problem is I need this for *thousands* of users. I am guessing thousands
> of classes are needed, but the question is, is this feasible? Could one
> machine ever handle this? How does this scale with either CBQ or HTB?
I should go for htb. And a perl of shell script to generate the commands :)
Stef
_______________________________________________
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-10-05 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 11:12 [LARTC] Thousands of classes, BW throttling and prioritizing?? Dare
2002-10-05 19:14 ` Stef Coene [this message]
2002-10-08 15:33 ` EGAL Vincent
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-103384534918589@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox