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] Minimum System Requirements?
Date: Sat, 26 Apr 2003 07:49:27 +0000	[thread overview]
Message-ID: <marc-lartc-105134345125406@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105131730313663@msgid-missing>

On Saturday 26 April 2003 02:33, ambitious_llama wrote:
> Hi,
>
> I'm new here and to mailing lists in general so apologies in advance for
> breaches in etiquette. I respond well to constructive criticism.
>
> I'm curious what kind of hardware requirements are needed for effective
> traffic shaping and control.
>
> For example, could a P200 with 48MB RAM handle limiting, shaping,
> NATing, and firewalling traffic from 5 - 6 clients on a 1.5Mbps/192kbps
> cable line?
It also depends on how many active classes you will have.  If you create 
5000000 classes but there are only 2 active classes, no problem.  But 5000000 
active classes will burn your CPU.  The same story for iptables rules and tc 
filters.

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/

      parent reply	other threads:[~2003-04-26  7:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-26  0:33 [LARTC] Minimum System Requirements? ambitious_llama
2003-04-26  1:37 ` Greg Scott
2003-04-26  7:49 ` 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-105134345125406@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.