Hi, Check out: tc -s filter show dev eth0. Where do you using prio qdisc in your testing scheme ( client --- INTERNET--- router --- shaper1 --- server )? As a hint - prio qdisc sends packets at WIRE speed, if you need to shape speed you should use tbf or htb/hfsc qdiscs in leaf classes( 1:1,1:2,1:3 ) 2009/5/25, Fabio Marcone <fabio.marcone@xxxxxxx>: > Hi, > I test this script: > #!/bin/bash > > tc qdisc del dev eth0 root > iptables -P INPUT ACCEPT > > tc qdisc add dev eth0 root handle 1: prio bands 3 > tc qdisc add dev eth0 parent 1:1 handle 2 sfq perturb 10 > tc qdisc add dev eth0 parent 1:2 handle 3 sfq perturb 10 > tc qdisc add dev eth0 parent 1:3 handle 4 sfq perturb 10 > #tc filter add dev eth0 protocol ip parent 1: prio 1 u32 match ip sport 80 > 0xffff flowid 1:1 > ##tc filter add dev eth0 protocol ip parent 1: prio 2 <your criteria_middle> > flowid 1:2 > #tc filter add dev eth0 protocol ip parent 1: prio 3 u32 match ip sport 81 > 0xffff flowid 1:3 > tc filter add dev eth0 protocol ip parent 1: prio 1 u32 classid 1:1 match ip > protocol 6 0xFF match ip sport 80 0xFFFF > tc filter add dev eth0 protocol ip parent 1: prio 2 u32 classid 1:3 match ip > protocol 6 0xFF match ip sport 81 0xFFFF > tc filter add dev eth0 protocol ip parent 1: prio 3 u32 match u8 0 0 flowid > 1:2 > > > I run 4 high priority processes (classid 1:1) and 1 low priority one > (classid 1:3). These are the result: > high proc1: 19.5K/s > high proc2: 5.71K/s > high proc3: 738B/s > high proc4: 12.8K/s > > low proc: 5.8 K/s > > I don't undestand: low process didn't stall and a high process used a > datarate << than low process. > > > Help, help, help! > > > Fabio -- Best regards Anatoly Muliarski -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
