gerald HUET wrote: > hello, > > Could you please explain what is a "non-work-conserving qdisc" and why it doesn't make sense ? A non-work-conserving qdisc is a qdisc that limits the total amount of bandwidth by stopping to hand out packets when some limit is reached. HFSC needs to know the length of the next packet to be sent to calculate the deadline, to get it it dequeues the inner qdiscs, peeks at the packet and requeues it again. When the inner qdisc is non-work-conserving it might refuse to hand the packet to HFSC and HFSC can not work properly. It does not make sense to do this since HFSC can operate in non-work-conserving mode itself (using upper-limit curves), so there is no need to attach further non-work-conserving qdiscs as leaves. > ----- Message d'origine ---- > De : Patrick McHardy <kaber@xxxxxxxxx> > À : Leo Wetz <spam-goes-to-dev-null@xxxxxxx> > Cc : lartc@xxxxxxxxxxxxxxx > Envoyé le : Mercredi, 13 Septembre 2006, 4h38mn 16s > Objet : Re: HFSC traffic loss bug, kernel 2.6.16.24 > > Leo Wetz wrote: > >>Sep 10 17:14:51 router kernel: HFSC: Non-work-conserving qdisc ? >>Sep 10 17:14:56 router kernel: printk: 266 messages suppressed. >>Sep 10 17:14:56 router kernel: HFSC: Non-work-conserving qdisc ? >>Sep 10 17:15:01 router kernel: printk: 259 messages suppressed. >>Sep 10 17:15:01 router kernel: HFSC: Non-work-conserving qdisc ? >>Sep 10 17:15:06 router kernel: printk: 294 messages suppressed. >>Sep 10 17:15:06 router kernel: HFSC: Non-work-conserving qdisc ? > > This is not a bug. You can't attach non-work-conserving qdiscs to > HFSC (and it doesn't make any sense). Just use classes instead > of adding HTB qdiscs. _______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
