# Base user class tc class add dev wivl4 parent 5:0 classid 5:130 hfsc ls m1 1536.0Kbit d 2000ms m2 512.00Kbit ul m2 1024Kbit # Priority queue tc qdisc add dev wivl4 parent 5:130 handle 134: prio bands 3 tc qdisc add dev wivl4 parent 134:1 handle 135: hfsc default 1 tc qdisc add dev wivl4 parent 134:2 handle 136: hfsc default 1 tc qdisc add dev wivl4 parent 134:3 handle 137: hfsc default 1 # VoIP / Interactive tc class add dev wivl4 parent 135: classid 135:1 hfsc sc umax 1500b dmax 30ms rate 128Kbit # Web tc class add dev wivl4 parent 136: classid 136:1 hfsc rt m2 512.00Kbit ls m2 512.0Kbit ul m2 1024Kbit # P2P tc class add dev wivl4 parent 137: classid 137:1 hfsc ls m2 1024.0Kbit ul m2 1024.0Kbit Does this look appropriate?
My understanding of HFSC is limited, but i'm fairly sure its similar to all other qdiscs in one respect that would make the config you have shown, not actually work as you've described. Each of those HFSC qdiscs is a seperate entity, no sharing will occur between those HFSC classes because each one belongs to a different qdisc. If you implemented this, the priority portion would likely work, but if all 3 classes were sending they would be trying for their individual max, resulting in a combined total send of 3072kbps. If you want what you've described then there would need to be some sort of way to define that same priority within one HSFC between the classes. I know HTB has the prio parameter but I've never found good documentation on HSFC and don't know if it has an equivalent. Of course all of what I said would be wrong if HSFC has inter-qdisc communication but I highly doubt that as it seems to go against the design of most qdiscs. What is there for good HSFC documentation out there right now anyways? Thanks, Jody _______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
