* [LARTC] my qos-cbq didn't work
@ 2002-12-12 23:09 James Ma
2002-12-13 17:04 ` Stef Coene
0 siblings, 1 reply; 2+ messages in thread
From: James Ma @ 2002-12-12 23:09 UTC (permalink / raw)
To: lartc
[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 2189 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [LARTC] my qos-cbq didn't work
2002-12-12 23:09 [LARTC] my qos-cbq didn't work James Ma
@ 2002-12-13 17:04 ` Stef Coene
0 siblings, 0 replies; 2+ messages in thread
From: Stef Coene @ 2002-12-13 17:04 UTC (permalink / raw)
To: lartc
On Friday 13 December 2002 00:09, James Ma wrote:
> 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?
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
--
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/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-12-13 17:04 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-12-12 23:09 [LARTC] my qos-cbq didn't work James Ma
2002-12-13 17:04 ` Stef Coene
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox