On Thu, Dec 06, 2001 at 08:28:07PM +0100, Stefan Rompf wrote: > Hi, > > tc qdisc add dev eth0 root handle 1: htb default 3 > > tc class add dev eth0 parent 1: classid 1:1 htb rate 20Mbit burst 4kB > tc qdisc add dev eth0 parent 1:1 sfq > > tc class add dev eth0 parent 1: classid 1:2 htb rate 3Mbit burst 2kB > tc qdisc add dev eth0 parent 1:2 sfq > > tc class add dev eth0 parent 1: classid 1:3 htb rate 77Mbit burst 150kB > tc qdisc add dev eth0 parent 1:3 sfq > > tc filter add dev eth0 parent 1:0 prio 7 protocol ip handle 1 fw classid > 1:1 > tc filter add dev eth0 parent 1:0 prio 7 protocol ip handle 2 fw classid > 1:2 > > /usr/local/sbin/iptables -t mangle -F OUTPUT > /usr/local/sbin/iptables -t mangle -A OUTPUT -p tcp --dport 9021 -j MARK > --set-mark 1 > /usr/local/sbin/iptables -t mangle -A OUTPUT -p tcp --dport 9022:9023 -j > MARK --set-mark 2 > > The network adaptor is connected to a 100MBit switch. When testing with > netio, I can send up to 370kB/sec through class 1:2 and up to 2,4MB/sec > via class 1:1, both measured by one/multiple instances of netio and the > rate output of "tc -s class dev eth0". This effect occurs with Linux > 2.4.16, kernel either compiled with HZ set to 100 or 1024, and of > course independant of the filter type used. During the tests, no packets > need to be dropped, htb just delays. I think your results are quite exact. The difference is because of different units. 370kB = 370 * 8 = 2.96 Mbit 2.4MB = 19.2 Mbit -- Daniel
