В Чтв, 21/05/2009 в 10:13 +0200, Fabio Marcone пишет: > Thanks for your reply. > I have just testing your script and I have some questions... > > Anatoly Muliarski wrote: > > Hi Fabio, > > > > You should do something like this: > > > > 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 <your > > criteria_high> 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 <your > > criteria_low> flowid 1:3 > > > why do you set a priority on filters? In my tests I always have been > used packet marking instead of "u32 match" method without prio > parameter. It is the same with priority? > > > That works in my system. > > > With your script I get the same result as mine: 2 parallel connections > (with different priority), one uses all bandwitdh and the other stalls > alternatively. > > perhaps there is a timeout mechanims that forse sending queued packets > although lower priority? This is exactly how PRIO works. Higher priority classes get dequeued first, so if there is something to dequeue forever then the lower priority classes would never dequeue. -- Покотиленко Костик <casper@xxxxxxxxxxxx> -- 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
