From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Lots amounts of classes to solve the DAP problem
Date: Tue, 22 Apr 2003 18:52:55 +0000 [thread overview]
Message-ID: <marc-lartc-105103762329433@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105103510025149@msgid-missing>
On Tuesday 22 April 2003 20:10, GoMi wrote:
> Stef, remember the problem about DAP users? i have written a little scrip
> to create 255 classes each for an ip of my segment, what do you think, am i
> mistaken anywhere? I am not sure i am getting the concept right. The idea
> is
> Total BW is lets say 255kbit
>
> root 1:0
>
> User 192.168.1.1:
>
> 1:1 2kbit ceil 255kbit
> / \
> / \
> 1kbit ceil 127kbit 1:2 1:4 1kbit ceil 128kbit
>
> pfifo 1:3 1:5 sfq
>
> User 192.168.1.2
>
> 1:6 2kbit ceil 255kbit
> / \
> / \
> 1kbit ceil 127kbit 1:7 1:8 1kbit ceil 128kbit
>
> pfifo 1:9 1:10 sfq
>
> And soo on 255 times...
Ok.
> I now the rate of the classes add up to be more than the total BW but since
> i am doing that for 2 ADSL working with multipath (loadbalanding) routing,
> i think there will never be all users using one interface. Dont know if my
> assumption is right..
Nothing bad will hapen if you have wrong rates for the parent.
I have a remark. You add the class directly to the root class. It's better
to add 1 class to the root qdisc and add the other classes to that class.
> To end up i have to set up a hashing table to create all the filters. The
> script to create the structure is the one on the bottom. What do you think?
> Am i going in the right direction or did i just completly missed what you
> were having in mind..? ( I have not set up the hashing table for filters
> yet)
The idea is ok :)
But I can't remember why you give each IP 2 subclasses? And why they can't
use the full bandwidth ?
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/
next prev parent reply other threads:[~2003-04-22 18:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 18:10 [LARTC] Lots amounts of classes to solve the DAP problem GoMi
2003-04-22 18:52 ` Stef Coene [this message]
2003-04-22 18:58 ` GoMi
2003-04-22 19:06 ` Stef Coene
2003-04-23 12:45 ` GoMi
2003-04-23 20:28 ` Stef Coene
2003-04-23 21:05 ` GoMi
2003-04-24 14:12 ` GoMi
2003-04-25 20:53 ` Stef Coene
2003-04-26 3:39 ` Rio Martin.
2003-04-26 4:50 ` Paul Evans
2003-04-26 8:01 ` Stef Coene
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-105103762329433@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.