Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Paul Caritj <pcaritj@riovia.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Scenario
Date: Tue, 07 Oct 2003 23:58:55 +0000	[thread overview]
Message-ID: <marc-lartc-106557165724868@msgid-missing> (raw)

Gents,

I've been thinking about shit for awhile, but thought I might defer to 
the group: What is the best wat to establish per-user bandwidth 
throttles in an ISP-like environment using TC? I am going to have to 
support something like 4000 users and I get kernel panics if I create 
that many QDISCs :)

-Paul

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

                 reply	other threads:[~2003-10-07 23:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-106557165724868@msgid-missing \
    --to=pcaritj@riovia.net \
    --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