Re: HTB performance improvement

[Andy Furniss <lists@xxxxxxxxxxxxxxxxxxxxxxx>]

gypsy wrote:
> gypsy wrote:
> > > tc qdisc add dev eth0.2 root handle 1: htb
> > > tc class add dev eth0.2 parent 1: classid 1:1 htb  rate 100000000 ceil
> > > 100000000 burst 1000000 quantum 1600
> > > tc class add dev eth0.2 parent 1:1 classid 1:10 htb prio 1 rate
> > > 70000000 ceil 70000000 burst 1000000 quantum 1600
> > > tc class add dev eth0.2 parent 1:1 classid 1:11 htb prio 2 rate
> > > 10000000 ceil 10000000 burst 1000000 quantum 1600
> > > tc class add dev eth0.2 parent 1:1 classid 1:12 htb prio 3 rate
> > > 10000000 ceil 10000000 burst 1000000 quantum 1600
>
> I just noticed that you're trying to shape "aliases".  You can't.  You
> must shape eth0 because you can't shape eth0.2.  I'm just repeating what
> I've heard/read, so do your own research.  But I bet you a quarter I'm
> right :)
> --

Could be vlans - in which case OP could try adding child b/pfifos to the 
leafs and use the limit parameter to specify buffer length.

HTB and HFSC both pick up default queuelengths from the device, but it's 
0 on vlans (they use 2 or 3 packet pfifos IIRC in this case).

I do notice there are no drops in the stats though, but it's still worth 
specifying queue length and type in the script.

Andy.

_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc