From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] sum of child rates exceeds parent rate
Date: Fri, 23 Jan 2004 20:56:56 +0000 [thread overview]
Message-ID: <200401232156.56520.stef.coene@docum.org> (raw)
In-Reply-To: <1073884201.40022c299ffd2@webmail1.maa.sify.net>
On Monday 19 January 2004 22:11, Damjan wrote:
> > It's the other way around. The class needs a token to send a packet. As
> > long as the class has tokens, it can send packets. If the class has used
> > all his tokens, it asks the parent if he has tokens left.
>
> Hmm, then you should correct this:
>
> http://www.docum.org/stef.coene/qos/tests/
> """
> If a child is using a token to send a packet, the same tocken is
> requested from the parent. So the child class is using the
> tokens/ctokens of it's parent. And without tokens, the parent can't
> give remaining bandwidth to it's child classes.
> """
It's not wrong. The word "remaining" is important. If the parent has no
tokens left, it can't give remaining bandwidth. But the child class can
always send packets equal to the rate even if the parent has no tokens left
so it can drag the parent (c)tokens negative.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-01-23 20:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 5:40 [LARTC] sum of child rates exceeds parent rate jayesh rathod
2004-01-12 17:31 ` Stef Coene
2004-01-13 10:13 ` arek
2004-01-13 21:20 ` Stef Coene
2004-01-13 22:58 ` arek
2004-01-14 22:00 ` Stef Coene
2004-01-19 21:11 ` Damjan
2004-01-19 23:03 ` Damjan
2004-01-23 20:56 ` Stef Coene [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=200401232156.56520.stef.coene@docum.org \
--to=stef.coene@docum.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox