LARTC - Oct 2004 - What is the reccomended minimum rate for leaf htb class for accurate operation?

Zviad O. Giorgadze wrote:
> # Class for GLOBAL traffic
> tc class add dev eth0 parent 1:1 classid 1:20 htb rate 115kbit ceil 1mbit
Does different rate / ceil for the root class make sense?
> # Classes for PC-s
> tc class add dev eth0 parent 1:20 classid 1:21 htb rate 48kbit ceil 1mbit
prio 2
> tc class add dev eth0 parent 1:20 classid 1:22 htb rate 24kbit ceil 1mbit
prio 3
> tc class add dev eth0 parent 1:20 classid 1:23 htb rate 12kbit ceil 1mbit
prio 5
> tc class add dev eth0 parent 1:20 classid 1:24 htb rate 12kbit ceil 1mbit
prio 5
> tc class add dev eth0 parent 1:20 classid 1:25 htb rate 12kbit ceil 1mbit
prio 5
I guess class 1:21 gets to borrow all the traffic up to 1mbit and the 
others get nothing at all. You really want that? These rates and prios 
don''t make sense to me, what do you intend to do?

I''d remove the prio parameter, increase global traffic class rate to 
1mbit, and increase PC class rates so that they add up to 1mbit.

Andreas
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Hi,

I''m trying to setup QoS in my TSL box. Following to mailing list
reccomendations I changed PSCHED_CPU but can''t get accurate shaping
with HTB. I have disabled HYSTERESIS also (by setting it to 0).
I have Intel Celeron 1.8Mhz (TSC supported I think).

******** My script ******
tc qdisc add dev eth0 root handle 1: htb default 22 r2q 10

# Class corresponding interface throughput
tc class add dev eth0 parent 1: classid 1:1 htb rate 100mbit ceil 100mbit

# Class for GLOBAL traffic
tc class add dev eth0 parent 1:1 classid 1:20 htb rate 115kbit ceil 1mbit

# Classes for PC-s
tc class add dev eth0 parent 1:20 classid 1:21 htb rate 48kbit ceil 1mbit prio 2
tc class add dev eth0 parent 1:20 classid 1:22 htb rate 24kbit ceil 1mbit prio 3
tc class add dev eth0 parent 1:20 classid 1:23 htb rate 12kbit ceil 1mbit prio 5
tc class add dev eth0 parent 1:20 classid 1:24 htb rate 12kbit ceil 1mbit prio 5
tc class add dev eth0 parent 1:20 classid 1:25 htb rate 12kbit ceil 1mbit prio 5

tc qdisc add dev eth0 parent 1:21 handle 21: pfifo
tc qdisc add dev eth0 parent 1:22 handle 22: pfifo
tc qdisc add dev eth0 parent 1:23 handle 23: pfifo
tc qdisc add dev eth0 parent 1:24 handle 24: pfifo
tc qdisc add dev eth0 parent 1:25 handle 25: pfifo

# Put flow to corresponding classes 
tc filter add dev eth0 protocol ip parent 1: u32 match ip dst 192.168.0.1 flowid
1:21
tc filter add dev eth0 protocol ip parent 1: u32 match ip dst 192.168.0.2 flowid
1:22
tc filter add dev eth0 protocol ip parent 1: u32 match ip dst 192.168.0.3 flowid
1:23
tc filter add dev eth0 protocol ip parent 1: u32 match ip dst 192.168.0.4 flowid
1:24
tc filter add dev eth0 protocol ip parent 1: u32 match ip dst 192.168.0.5 flowid
1:25
******** End of script *********


What is the reccomended minimum rate for leaf htb class for accurate operation?
Can I change somesing in my script to get more accurate results?

Regrads,

Zviad



_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

So what about minimum rate?
I have rate 13kbit. My connection is sometimes congested and and I have much
loss of packets which are going from clients to the internet trough htb box.
From box to the internet there is no any packet loss. Is this normal using
HTB with congested connection?
----- Original Message ----- 
From: "Andreas Klauer" <Andreas.Klauer@metamorpher.de>
To: <zgiorgadze@gol.ge>
Cc: <lartc@mailman.ds9a.nl>
Sent: Wednesday, October 06, 2004 10:14 AM
Subject: Re: [LARTC] What is the reccomended minimum rate for leaf htb class
for accurate operation?

> Zviad O. Giorgadze wrote:
> > # Class for GLOBAL traffic
> > tc class add dev eth0 parent 1:1 classid 1:20 htb rate 115kbit ceil
1mbit
>
> Does different rate / ceil for the root class make sense?
>
> > # Classes for PC-s
> > tc class add dev eth0 parent 1:20 classid 1:21 htb rate 48kbit ceil
1mbit prio 2
> > tc class add dev eth0 parent 1:20 classid 1:22 htb rate 24kbit ceil
1mbit prio 3
> > tc class add dev eth0 parent 1:20 classid 1:23 htb rate 12kbit ceil
1mbit prio 5
> > tc class add dev eth0 parent 1:20 classid 1:24 htb rate 12kbit ceil
1mbit prio 5
> > tc class add dev eth0 parent 1:20 classid 1:25 htb rate 12kbit ceil
1mbit prio 5
>
> I guess class 1:21 gets to borrow all the traffic up to 1mbit and the
> others get nothing at all. You really want that? These rates and prios
> don''t make sense to me, what do you intend to do?
>
> I''d remove the prio parameter, increase global traffic class rate
to
> 1mbit, and increase PC class rates so that they add up to 1mbit.
>
> Andreas
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

"Zviad O. Giorgadze" wrote:
> # Put flow to corresponding classes
> tc filter add dev eth0 protocol ip parent 1: u32 match ip dst 192.168.0.1
flowid 1:21
> tc filter add dev eth0 protocol ip parent 1: u32 match ip dst 192.168.0.2
flowid 1:22
> tc filter add dev eth0 protocol ip parent 1: u32 match ip dst 192.168.0.3
flowid 1:23
> tc filter add dev eth0 protocol ip parent 1: u32 match ip dst 192.168.0.4
flowid 1:24
> tc filter add dev eth0 protocol ip parent 1: u32 match ip dst 192.168.0.5
flowid 1:25
If you are NATting, there is no 192.168.0.anything because the address
has been NATted.

If not, add a prio parameter to these filter lines where prio is NOT 0.

If you are NATting, use an iptables mark and filter on fwmark.

Other than that, I can''t help you.

gypsy
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

On Wednesday 06 October 2004 10:14, Andreas Klauer
wrote:
> Zviad O. Giorgadze wrote:
> > # Class for GLOBAL traffic
> > tc class add dev eth0 parent 1:1 classid 1:20 htb rate 115kbit ceil
1mbit
>
> Does different rate / ceil for the root class make sense?
No.
Same for the classes attached to the root qdisc.  They can not share 
bandwidth.  So your basi setup should be:
root htb qdisc
   htb class with ceil = rate = link bandwidth
      other classes

Stef

-- 
stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

>> Does different rate / ceil for the root class make sense?
>No.
>Same for the classes attached to the root qdisc.  They can not share 
>bandwidth.  So your basi setup should be:
>root htb qdisc
>   htb class with ceil = rate = link bandwidth
>      other classes
So following script is reccomended?
 
tc qdisc add dev eth0 root handle 1: htb default 11 r2q 10

# Class corresponding external interface throughput (for 115kbit ADSL)
tc class add dev eth0 parent 1: classid 1:1 htb rate 115kbit ceil 115kbit

# Classes for PC-s
tc class add dev eth0 parent 1:1 classid 1:11 htb rate 55kbit ceil 115kbit prio
2
tc class add dev eth0 parent 1:1 classid 1:12 htb rate 48kbit ceil 115kbit prio
3
tc class add dev eth0 parent 1:1 classid 1:13 htb rate 12kbit ceil 115kbit prio
4
#End if script

What can I do if the same interface (eth0) is used for other purposes (internal
traffic generated from local servers)?
If HTB class has the highest ceil set to 115kbit, how can I define other classes
for example for internal traffic?

Zviad


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/