Hi All, I have a setup similar to: eth1 - 100mb/s eth1.2 - local VoIP @ 100mb/s eth1.3 - local Guest eth1.4 - local Business eth1.5 - MPLS @ 3mb/s Am I correct in thinking my TC needs to hang off only eth1 so that it can arbitrate traffic across the entire interface? Something like the following (may have typos). I use a pfifo queue to get packets out quickest for realtime and an sfq where there are multiple long-term connections (tcp). Examining the queue drop counters would tell me if they are too short? tc qdisc add dev eth1 root handle 1: hfsc default 999 # NIC tc class add dev eth1 parent 1:1 handle 1:10 ls rate 100mbit ul rate 90mbit # VLAN2, small UDP VoIP packets tc class add dev eth1 parent 1:10 handle 1:20 ls rate 20mbit tc qdisc add dev eth1 parent 1:20 handle 21: pfifo limit 20 # VLAN3 Guest tc class add dev eth1 parent 1:10 handle 1:30 ls rate 20mbit tc qdisc add dev eth1 parent 1:30 handle 30: sfq quantum 1500b limit 100 # VLAN4 Business tc class add dev eth1 parent 1:10 handle 1:40 ls rate 20mbit tc qdisc add dev eth1 parent 1:40 handle 40: sfq quantum 1500b limit 100 # VLAN5 MPLS tc class add dev eth1 parent 1:10 handle 1:50 ls rate 3mbit ul rate 3mbit # Realtime VoIP tc class add dev eth1 parent 1:50 handle 1:51 ls rate 1mbit rt rate 100kbit tc qdisc add dev eth1 parent 1:51 handle 51: pfifo limit 50 # Realtime Video tc class add dev eth1 parent 1:50 handle 1:52 ls rate lmbit rt rate 600kbit tc qdisc add dev eth1 parent 1:52 handle 52: pfifo limit 50 # Bulk tc class add dev eth1 parent 1:50 handle 1:53 ls rate lmbit tc qdisc add dev eth1 parent 1:53 handle 53: sfq quantum 1500b limit 100 Thanks for any help -- lee -- To unsubscribe from this list: send the line "unsubscribe lartc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
