Skip to contentSkip to conversation

my qos-cbq didn't work

LARTC James Ma 2 participants 2 messages Dec 12, 2002 – Dec 13, 2002

lore
Share & tools
lore

James Ma

author
#0 lore raw

Hi, All,

I implemented the following qos scripts in my Linux gateway (redhat7.3, kernel 2.4.18), put ftp server (10.10.3.49) on one side (eth0 nic) and ftp client (10.10.5.3) on the other side (eth1 nic). I tried to up load a file (211kbytes) from client to ftp server. I wanted to see a 22kbps transmission rate. Quite surprise, the ftp client showed transmission rate as 6.8e+02 kbytes/s (211k transmitted in 0.3 seconds). It was the same as it without qos implementation. So the conclusion is the QoS was not working at all.

Could anybody tell me what's wrong with the setting?

Thanks,

James

#!/bin/sh

OPTION="allot 1514 maxburst 20 avpkt 500"

tc qdisc del dev eth0 root

tc qdisc add dev eth0 root handle 10: cbq bandwidth 10mbit avpkt 500

tc class add dev eth0 parent 10:0 classid 10:2 cbq bandwidth 10mbit rate 22kbps $OPTION prio 3 bounded

tc qdisc add dev eth0 parent 10:2 handle 20: cbq bandwidth 10mbit allot 1514 avpkt 500

tc class add dev eth0 parent 20: classid 20:10 cbq bandwidth 10mbit rate 11kbps $OPTION prio 3 bounded

tc class add dev eth0 parent 20: classid 20:20 cbq bandwidth 10mbit rate 11kbps $OPTION prio3 bounded

tc filter add dev eth0 parent 10: protocol ip prio 3 u32 match ip tos 0xa0 0xff flowid 10:2

tc filter add dev eth0 parent 10: protocol ip prio 3 u32 match ip src 10.10.5.3/24 flowid 10:2

tc filter add dev eth0 parent 20: protocol ip prio 3 u32 match ip tos 0xa0 0xff flowid 20:10

tc filter add dev eth0 parent 20: protocol ip prio 3 u32 match ip src 10.10.5.3/24 flowid 20:20

#1 lore raw
Quoted 11 lines · James Ma

Hi, All,

I implemented the following qos scripts in my Linux gateway (redhat7.3, kernel 2.4.18), put ftp server (10.10.3.49) on one side (eth0 nic) and ftp client (10.10.5.3) on the other side (eth1 nic). I tried to up load a file (211kbytes) from client to ftp server. I wanted to see a 22kbps transmission rate. Quite surprise, the ftp client showed transmission rate as 6.8e+02 kbytes/s (211k transmitted in 0.3 seconds). It was the same as it without qos implementation. So the conclusion is the QoS was not working at all.

Quoted 1 line

Could anybody tell me what's wrong with the setting?

Yes I can. You have a cbq qdisc attached to a cbq class. This will cause some problems. I did some test about this (www.docum.org on the test page). It's better to create only classes :

tc qdisc add dev eth0 root handle 10: cbq bandwidth 10mbit avpkt 500

tc class add dev eth0 parent 10:0 classid 10:2 cbq bandwidth 10mbit rate 22kbps $OPTION prio 3 bounded

tc class add dev eth0 parent 10:2 classid 10:10 cbq bandwidth 10mbit rate 11kbps $OPTION prio 3 bounded

tc class add dev eth0 parent 10:2 classid 10:20 cbq bandwidth 10mbit rate 11kbps $OPTION prio3 bounded

If you bound 10:10 and 10:20 they are not able to borrow bandwidth from each other.

Stef

Signature · 8 lines
[email protected]
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/