Hi. I'm using this new "flow" filter: (http://www.mail-archive.com/netdev@xxxxxxxxxxxxxxx/msg60638.html). It is configuration as above: tc filter flow classify packets in the sfq. It works (as it seems) fine. But only until there is some traffic in the queue. When there is some interruption in the packets flow (for a while) something goes wrong and the queue blocks. From that moment onward nothing goes trough. It is very annoying. You have to remove sfq to resume traffic. Is anybody using this new filter which sfq? My configuration: gentoo, kernel 2.6.26.7 + imq patch + l7 patch, glibc 2.7, iproute2 2.6.26. Shaping is done on ethernet (e1000 card) but as I see on the ifb nothing changes. There are htb 3 classes with sfq as their qdiscs. It is simple, something like: tc qdisc add dev $DEV root handle 1: htb default 4 tc class add dev $DEV parent 1: classid 1:1 htb rate 78kbps ceil 78kbps overhead 0 linklayer atm tc class add dev $DEV parent 1:1 classid 1:2 htb rate 20kbps ceil 20kbps overhead 0 linklayer atm prio 3 tc class add dev $DEV parent 1:1 classid 1:3 ... tc class add dev $DEV parent 1:1 classid 1:4 ... tc qdisc add dev $DEV parent 1:2 handle 2: sfq quantum 64 tc qdisc add dev $DEV parent 1:3 handle 3: sfq tc qdisc add dev $DEV parent 1:4 handle 4: sfq tc filter add dev $DEV parent 1: .... .... tc filter add dev $DEV parent 2: protocol ip handle 1 prio 12 flow \ hash keys dst,proto,proto-dst divisor 128 tc filter add dev $DEV parent 3: protocol ip handle 1 prio 12 flow \ hash keys dst,proto,proto-dst divisor 128 tc filter add dev $DEV parent 4: protocol ip handle 1 prio 12 flow \ hash keys nfct-src,nfct-dst,proto,nfct-proto-src,nfct-proto-dst divisor 128 I'm not sure where is the bug - in the flow filter or in the sfq qdisc. Regards Krzysiek ---------------------------------------------------------------------- Wymysl wierszyk, wygraj cyfrowke! Sprawdz >>> http://link.interia.pl/f1f5a -- To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
