Hi, below are some test results from implementing a prio qdisc 'that is also below'.
The qdisc is attacted to a vlan interface for my external network. Both tests were run
at the same time.
The links are policed at 6.0M 'by our provider'.
192.168.70.1 --> 192.168.30.1
My question is: If using a prio qdisc should'nt the iperf run with a tos of b8
have the majority of the bandwidth?

thx jason
 

./iperf -c 192.168.30.1 -t 20 -i 5 --tos 0xb8  [dscp 46] ef
 
[  5] local 192.168.70.1 port 33483 connected with 192.168.30.1 port 5001
[ ID] Interval       Transfer     Bandwidth
[  5]  0.0- 5.0 sec  2.80 MBytes  4.69 Mbits/sec
[  5]  5.0-10.0 sec   968 KBytes  1.59 Mbits/sec
[  5] 10.0-15.0 sec  1.73 MBytes  2.90 Mbits/sec
[  5] 15.0-20.0 sec  2.05 MBytes  3.45 Mbits/sec
[  5]  0.0-20.2 sec  7.53 MBytes  3.13 Mbits/sec
 
 ./iperf -c 192.168.30.1 -t 20 -i 5 --tos 0x28 [dscp 10] af11
 
[  5] local 192.168.70.1 port 33484 connected with 192.168.30.1 port 5001
[ ID] Interval       Transfer     Bandwidth
[  5]  0.0- 5.0 sec  2.13 MBytes  3.58 Mbits/sec
[  5]  5.0-10.0 sec  2.37 MBytes  3.97 Mbits/sec
[  5] 10.0-15.0 sec  2.20 MBytes  3.68 Mbits/sec
[  5] 15.0-20.0 sec  1.75 MBytes  2.94 Mbits/sec
[  5]  0.0-20.3 sec  8.45 MBytes  3.49 Mbits/sec
 

#!/bin/sh
tc qdisc del dev eth0.2 root
tc qdisc add dev eth0.2 root handle 1: prio
tc filter add dev eth0.2 parent 1:0 prio 1 protocol ip u32 \
        match ip tos 0xb8 0xfc  flowid 1:1
tc filter add dev eth0.2 parent 1:0 prio 2 protocol ip u32 \
        match ip tos 0x68 0xfc flowid 1:2
tc filter add dev eth0.2 parent 1:0 prio 3 protocol ip u32 \
        match ip tos 0x28 0xfc  flowid 1:3
tc filter add dev eth0.2 parent 1:0 prio 3 protocol ip u32 \
        match ip tos 0x00 0xfc flowid 1:3
 
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

Reply via email to