Emanuele Colombo wrote: >> What about using HTB and *then* using PRIO as its leaf class? You would >> use HTB only to shape. > > Hi! > I tried your solution and it seems to work. Yet i'm experiencing an > unexpected behaviour: when i try to fill the highest priority queue > (expecting the lower priority traffic to starve), i see that the > higher priority queue starts to grow, while some lower priority > packets are served. This means that upon congestion of the link, the > shaper stops working properly and does not apply a strict priority > policy. > > I was wondering about the granularity of the service: in fact it may > happen that, if the granularity is, say, 5 packets, the scheduler sees > the higher priority queue empty, and it serves a "train" of 5 packets > from the lower priority queue; while it is serving those packets, new > packets arrive in the high priority queue, and have to wait until the > scheuler have fully served the lower priority train. > To avoid such a behaviour, i looked for a parameter that sets the > granularity, but the documentation is not that clear about it: what > are the parameters that set the granularity? Is it a problem of prio > or of htb? One thing you may try is to recompile sch_htb with HTB_HYSTERESIS[1] set to 0. You'll get improved performance on slower links where you need the accurancy. [1] http://edseek.com/~jasonb/articles/traffic_shaping/buildkernel.html _______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
