From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: Re : [LARTC] HFSC traffic loss bug, kernel 2.6.16.24
Date: Fri, 15 Sep 2006 04:50:54 +0000 [thread overview]
Message-ID: <450A312E.8090900@trash.net> (raw)
In-Reply-To: <20060910152735.81EB3405C@outpost.ds9a.nl>
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@trash.net>
> À : Leo Wetz <spam-goes-to-dev-null@gmx.net>
> Cc : lartc@mailman.ds9a.nl
> Envoyé le : Mercredi, 13 Septembre 2006, 4h38mn 16s
> Objet : Re: [LARTC] 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@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-09-15 4:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 15:28 [LARTC] HFSC traffic loss bug, kernel 2.6.16.24 Leo Wetz
2006-09-13 16:38 ` Patrick McHardy
2006-09-14 11:52 ` Re : " gerald HUET
2006-09-15 4:50 ` Patrick McHardy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=450A312E.8090900@trash.net \
--to=kaber@trash.net \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.