From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problem while using HTB bandwidth limitation
Date: Mon, 01 Sep 2003 17:41:30 +0000 [thread overview]
Message-ID: <marc-lartc-106243817115991@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106242135331948@msgid-missing>
On Monday 01 September 2003 15:02, Nimit Gupta wrote:
> Hello everyone,
>
> I am using htb to shape bandwidth but I can see heavy ups and downs from
> the specified limit. I have seen users with 24Kbit limitation can reach
> upto 36Kbit.
>
> Can there be any problem if I set 10 classes each restricted to 24kbit
> under a class which has been restricted to 128Kbit.
>
> My point is what happens if total of child classes, is more than the
> parent class itself. Does it distribute fairly ie equally to all 10
> classes or will there be a problem.
Each class should be able to het 1/10 of 128kbit. But it can be bursty.
> I want it to be this way because I know not all 10 people use it
> simultaneously there can be 7 people at max who will be browsing at same
> time.
>
> Here are some rules:
>
> #Creating root qdisc
> tc qdisc add dev eth0 root handle 1: htb default 4000
>
> tc c a dev eth0 parent 1: classid 1:1 htb rate 192Kbit burst 15Kbit
>
> #Rules for default class
> tc c a dev eth0 parent 1:1 classid 1:4000 htb rate 16Kbit burst 10Kbit
> tc q a dev eth0 parent 1:4000 handle 4000: sfq perturb 10
>
> # Rules for each of the 10 machines
> tc c a dev eth0 parent 1:1 classid 1:$C_ID htb rate 24Kbit burst 10Kbit
>
> tc q a dev eth0 parent 1:$C_ID handle $C_ID: sfq perturb 10
> tc f a dev eth0 protocol ip parent 1: prio 5 u32 match ip dst $IP
> classid 1:$C_ID
Try to remove the burst parameter. And if you have a 192Kbit link, you should
limit all bandwidth to 188kbit so YOU are the bottleneck on the link and not
the modem.
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-09-01 17:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 13:14 [LARTC] Problem while using HTB bandwidth limitation Nimit Gupta
2003-09-01 17:41 ` Stef Coene [this message]
2003-09-02 4:46 ` Martin A. Brown
2003-09-02 4:47 ` Nimit Gupta
2003-09-02 5:51 ` Nimit Gupta
2003-09-02 16:52 ` Stef Coene
2003-09-03 4:56 ` Nimit Gupta
2003-09-08 16:48 ` 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-106243817115991@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.