From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] bnig number of interfaces and upstream limit
Date: Sun, 11 Aug 2002 18:02:24 +0000 [thread overview]
Message-ID: <marc-lartc-102908902231040@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102901727632275@msgid-missing>
> Downstream is easy - I just add htb rule on user pppX interface
> and that's all. 100 rules for 100 clients.
>
> Upstream seems be big problem because AFAIK htb (cbq, too) must
> be attached to outgoing interface which means that in my
> case for each client there is 99 potential outgoing interfaces.
>
> This means that I need to setup 10k rules for only 100 clients
> (100 rules for each pppX interface) !
>
> I'm not sure but 10k rules (u32 filter) is rather big number
> for typical PC (or maybe I'm wrong and 10k rules is small
> thing to process for ie. single duron 800MHz, 256MB RAM?).
>
> Any ideas how to do such limiting in better way?
You can use the imq device to catch all incoming traffic. You can create 10
subclasses and put each client data in 1 subclass. Or you can use the
ingress qdisc and use the policers in the filters to throttle incoming
traffic per interface.
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-08-11 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-10 22:06 [LARTC] bnig number of interfaces and upstream limit Arkadiusz Miskiewicz
2002-08-11 10:41 ` Arkadiusz Miskiewicz
2002-08-11 18:02 ` 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-102908902231040@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.