From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB: quantum of class 100001 is small. Consider r2q change
Date: Sat, 11 Oct 2003 18:10:10 +0000 [thread overview]
Message-ID: <marc-lartc-106589591319042@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106589490618377@msgid-missing>
On Saturday 11 October 2003 19:54, Dragoº Cintezã wrote:
> Salut lartc (lartc@mailman.ds9a.nl),
>
>
> 18:12:52 kernel HTB init, kernel part version 3.10
> 18:12:52 kernel HTB: quantum of class 100001 is small. Consider r2q change.
> 18:12:52 kernel HTB: quantum of class 100002 is small. Consider r2q change.
> 18:12:52 kernel HTB: quantum of class 100003 is small. Consider r2q change.
> 18:12:52 kernel HTB: quantum of class 100004 is small. Consider r2q change.
> 18:12:53 kernel HTB: quantum of class 100005 is small. Consider r2q change.
> 18:12:53 kernel HTB: quantum of class 100006 is small. Consider r2q change.
> 18:12:53 kernel HTB: quantum of class 100007 is small. Consider r2q change.
>
> I get this in my logs . I tried to specify another r2q But i did not
> succed. Can anyone help me please?
>
> Here's my script:
>
> tc qdisc add dev eth1 root handle 10: htb
> tc class add dev eth1 parent 10: classid 10:10 htb rate 125kbit ceil
> 125kbit burst 1k
>
> tc class add dev eth1 parent 10:10 classid 10:1 htb rate 18kbit ceil
> 125kbit prio 2 burst 1k tc qdisc add dev eth1 parent 10:1 handle 1: sfq
> perturb 10
> tc filter add dev eth1 parent 10: protocol ip handle 1 fw classid 10:1
> tc filter add dev eth1 parent 10: protocol ip prio 2 u32 match ip src
> 192.168.1.1 flowid 10:1 tc filter add dev eth1 parent 10: protocol ip prio
> 3 u32 match ip dst 192.168.1.1 flowid 10:1
>
> tc class add dev eth1 parent 10:10 classid 10:2 htb rate 18kbit ceil
> 125kbit prio 2 burst 1k tc qdisc add dev eth1 parent 10:2 handle 2: sfq
> perturb 10
> tc filter add dev eth1 parent 10: protocol ip handle 1 fw classid 10:1
> tc filter add dev eth1 parent 10: protocol ip prio 2 u32 match ip src
> 192.168.1.2 flowid 10:2 tc filter add dev eth1 parent 10: protocol ip prio
> 3 u32 match ip dst 192.168.1.2 flowid 10:2
>
> .....
>
> tc class add dev eth1 parent 10:10 classid 10:7 htb rate 18kbit ceil
> 125kbit prio 2 burst 1k tc qdisc add dev eth1 parent 10:7 handle 7: sfq
> perturb 10
> tc filter add dev eth1 parent 10: protocol ip handle 7 fw classid 10:7
> tc filter add dev eth1 parent 10: protocol ip prio 2 u32 match ip src
> 192.168.1.7 flowid 10:7 tc filter add dev eth1 parent 10: protocol ip prio
> 3 u32 match ip dst 192.168.1.7 flowid 10:7
I have some info on the faq page on docum.org about r2q and quantum.
The rules (for each class) :
quantum = rate (in byte) / r2q
and
1500 < quantum < 60000.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-10-11 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-11 17:54 [LARTC] HTB: quantum of class 100001 is small. Consider r2q change =?unknown-8bit?q?Drago=C2=BA_Cintez=C3=A3?=
2003-10-11 18:10 ` 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-106589591319042@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox