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] HTB with SFQ in leaf classes. & setups question
Date: Tue, 10 Dec 2002 19:01:30 +0000	[thread overview]
Message-ID: <marc-lartc-103954698118544@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103954631317647@msgid-missing>

On Tuesday 10 December 2002 19:48, lartc@e-apollo.lv wrote:
> Hello,
>
> I wrote something yesterday.
> Now the situation is even worse. Communicatin with some clients wont work
> at all until i restart the traffic shaping box.
> (It works for some hours, then suddenly dies (meaning the client cant be
> pinged. Suspected at peak hours)
> Maybe the computer resources are weak, maybe its setup faulty
Do you have any errors in dmesg?  And how is the memory and cpu usage ?

> It's a PIII 1.13Ghz, 512mb ram.
>
> ~250 users are shaped. From 32kbit/s to 256kbit/s
> Traffic is to be shaped as following:
>
> (1) [ 8 Mbit. In (internet->us) ]
>     `- (2) client 1 .
>
>    |                `` (3) Local Traffic (can borrow from Foreign)
>    |                 ` (4) Foreign Traffic
>
>     `- (2) client 2 .
>
>    |                `` (3) Local Traffic (can borrow from Foreign)
>    |                 ` (4) Foreign Traffic
>
>     `- (2) client N .
>                     `` (3) Local Traffic (can borrow from Foreign)
>                      ` (4) Foreign Traffic
>
> To achieve the following i have set it up as:
>
> # root handle for 8Mbit (1)
> /sbin/tc qdisc add dev eth2 root handle 1: htb
>
> # client class (2) with maximum allowed traffic (256kbit for example)
> /sbin/tc class add dev eth2 parent 1: classid 1:1 htb rate 256kbit ceil
> 256kbit
>
> # Local traffic (3) class (Local should work at maximum, tho if Foreign is
> used, it should get 1/4th)
> # So, Foreign should be 1/4th of Local traffic.
> # (Is this class correct? Its meant to have 192kbit/s for Local traffic and
> if Foreign is not used
> # then it can have 256kbit)
> /sbin/tc class add dev eth2 parent 1:1 classid 1:2 htb rate 192kbit ceil
> 256kbit
>
> # Foreign traffic (4) class (Not more than 64kbit/s)
> /sbin/tc class add dev eth2 parent 1:1 classid 1:3 htb rate 64kbit ceil
> 64kbit
>
> # Now I attach SFQ to classes
> # (to Local traffic class)
> /sbin/tc qdisc add dev eth2 parent 1:2 handle 1500: sfq perturb 10
>
> # (to Foreign traffic class)
> /sbin/tc qdisc add dev eth2 parent 1:3 handle 1501: sft perturb 10
>
>
> # Now add filters
> # (wont write)
> # flowid 1:2
> # flowid 1:#
>
> .. everything repeated for all users. (changing data rate and class IDs)
>
> Is there anything wrong with my setup?
No.  But maye you can create 1 super class (but I don't think it will change a 
lot) :
root qdisc 1:0
  class 1:10    rate = 8mbit = ceil 
    class 1:1    rate = 256 = ceil
      class 1:2    rate = 192, ceil = 256
      class 1:3    rate = 64, ceil = 256
    class ....

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/

      reply	other threads:[~2002-12-10 19:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10 18:48 [LARTC] HTB with SFQ in leaf classes. & setups question lartc
2002-12-10 19:01 ` 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-103954698118544@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.