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] herz the script that i have done.
Date: Sun, 15 Jun 2003 18:59:25 +0000	[thread overview]
Message-ID: <marc-lartc-105570366914375@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105567787128739@msgid-missing>

On Sunday 15 June 2003 08:27, Trevor Warren wrote:
> Stef....;)
>
>  Hats off to you. I am zapped as to how did you figure out the
> "isolated" class wasn't working???.
I did some filter tests to see if you can split the traffic in different 
classes and how you have to do this.  At the same time I tried the isolated 
parameter.  If you have an isolated, not-bounded class, there is no shaping.  
As long as the classes are bounded, everything is working like it should be :
http://www.docum.org/stef.coene/qos/tests/cbq/filter.html

>  Anyway Stef, i am glad that you have detected something without my
> telling you. Have changed the same and have restarted the server. Lets
> see. Its night time here in Bombay, hence am playing around with the
> production machine.
>
>  Stef, I need to traffic shape for my 1000 odd users on the network. Is
> there a way to do it by having static qdisc's /classes/filters inserted.
It depends on how much control you want to have.  If you want to have tied 
control, you have to create 1 class (filter) / user.  Or you can try the wrr 
qdisc (you can find a link on www.docum.org).  This qdisc can create 1 class 
for each filter/mac-address it sees and punish big downloaders by limiting 
the rate.

>  Also, can i do them on the fly by having them login cia a SUID ROOT ph
> page and then get web access and thus adding/deleting these qdisc's
> /classes/filters on the fly???.
Or you use a tc binary with a sticky bit so any user can execute tc and the 
execution is done as user root.

Just wondering, you make all classes bounded.  So they can not borrow 
bandwidth from each other.  But if you do this, why do you create the classes 
1:1 and 1:2 ??

And you use 2 filters to put the packets in the end class.  You can do this in 
1 step so you need only 1 filter.  Just put the packets directly in the end 
class.  If you are interested, I did some tests with filters and how the 
weight parameter influence the sharing between the filters :
http://www.docum.org/stef.coene/qos/tests/cbq/splitting/splitting.html

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-06-15 18:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-14 23:58 [LARTC] herz the script that i have done Trevor Warren
2003-06-15  6:39 ` Trevor Warren
2003-06-15 17:56 ` Stef Coene
2003-06-15 18:59 ` Stef Coene [this message]
2003-06-15 19:20 ` Trevor Warren
2003-06-15 20:01 ` Trevor Warren
2003-06-15 20:58 ` Trevor Warren
2003-06-16  7:28 ` Stef Coene
2003-06-16  8:22 ` Stef Coene
2003-06-16  9:52 ` Stef Coene
2003-06-16 15:39 ` Trevor Warren
2003-06-17  0:35 ` Trevor Warren
2003-06-17 17:36 ` Stef Coene
2003-06-18 20:19 ` Trevor Warren

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-105570366914375@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.