I just did the tests and these are my results : (I use ttcp to test) for class 20:1 = 71.90 KB/sec (575.2Kbit/sec) for class 20:2 = 134.05 KB/sec (1072.4Kbit/s) The numbers are not correct, but I think it's just CBQ that's not very accurate when you use the bounded paramter. I got the same results when I use everywhere prio8 and put class 20:2 on qdisc 20:0. So it's a CBQ accuracy problem. -- Staf More QOS info : http://users.belgacom.net/staf/ > Juergen wrote: > > I try to use iproute to control my bandwidth less than 3MB, but > something happen. > list below is my config > ---------------------------------------------------------------------- > tc qdisc add dev eth1 root handle 20: cbq bandwidth 10Mbit avpkt 1000 > > tc class add dev eth1 parent 20:0 classid 20:1 cbq bandwidth 10Mbit > rate \ > 1Mbit allot 1514 weight 100Kbit prio 8 maxburst 20 avpkt 1000 bounded > > tc class add dev eth1 parent 20:1 classid 20:2 cbq bandwidth 10Mbit > rate \ > 3Mbit allot 1514 weight 200Kbit prio 5 maxburst 20 avpkt 1000 bounded > > tc filter add dev eth1 parent 20:0 protocol ip prio 100 u32 match ip > src \ > 192.168.0.1 flowid 20:1 > > tc filter add dev eth1 parent 20:0 protocol ip prio 25 u32 match ip > src \ > 192.168.0.2 flowid 20:2 > ---------------------------------------------------------------------- > I use download file to test this function. > But the really situation about the bandwidth is ... > 1MB(20:1) is 1.5Mbit > 3MB(20:2)is 4.6Mbit > Have anyone met this kind of problem before????? > And how to solve this problem?????
