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] quantity of qdisc
Date: Tue, 14 May 2002 08:45:31 +0000	[thread overview]
Message-ID: <marc-lartc-102136600130323@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102100163310897@msgid-missing>

On Tuesday 14 May 2002 04:20, hanhbnetfilter wrote:
> Dear sir:
>   There is a lot of work stations in my lan. Every one
> should be seperate set bandwidth limit,so qdisc(class)
> will be very large.
>   These workstations can be included in several
> groups,iptables rule can be set and mark can be used
> in filter,so class can be reduced,but in these groups
> the member of the group still has itself bandwidth
> limit.
>   The quantity of qdisc(class) will impact the
> performance.I do not know how much it impact.100 and
> 200 or 500 must be different.
>   which qdisc and class rules should i use?
> please tell me how can i do
HTB3 is still beta, but fast.  Even faster then CBQ.
For the filters, you can use one fw filter.  This filter will use the 
iptables mark direclty to find the class.  If you mark a packet with 9, it 
will end in class :9.  Very easy.  So all filter logic is in the iptables 
rules.  But you still have to create all the classes.

Or you can use the wrr qdisc (http://wipl-wrr.sourceforge.net).   This qdisc 
will create a class for each ip it sees.  So you don't need to create the 
classes and the filters yourself.

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

      parent reply	other threads:[~2002-05-14  8:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-10  3:32 [LARTC] quantity of qdisc hanhbnetfilter
2002-05-10  8:35 ` Stef Coene
2002-05-14  2:20 ` hanhbnetfilter
2002-05-14  8:45 ` 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-102136600130323@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.