From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] priorities + htb
Date: Sat, 19 Jun 2004 20:36:11 +0000 [thread overview]
Message-ID: <200406192236.11972.stef.coene@docum.org> (raw)
In-Reply-To: <20040618085411.GA25143@oasis.frogfoot.net>
On Friday 18 June 2004 13:12, pljosh wrote:
> U¿ytkownik Abraham van der Merwe napisa³:
> > Hi!
> > How does prioritization work when you've got a tree structure, e.g.
> >
> > +-- class_a rate 64kbit prio 1
> >
> > | +-- class_a1 rate 32kbit prio 1
> > |
> > | `-- class_a2 rate 32kbit prio 2
> >
> > `-- class_b rate 64kbit prio 2
The prio of class class_a is never used and does not matter.
> HTB means: __Hierarchical__ Token Bucket so it is more like this:
> > (b) all packets matching a1, a2 are prio 1, then a1 is given a higher
> > priority than a2
> >
> > (iow, multiple layers of prioritization exist)
>
> But "prio" is used when there is some some unused BW that could be
> splited for borrowing (for classes which have ceil higher than rate).
Htb is used for 2 things:
- class with lowest prio will get the lowest latancy (if and only if this
class is not sending more data then the tate)
- class will lowest prio will get the remaining bandwidth from the parent
after each child class is sending his rate.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-06-19 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 8:54 [LARTC] priorities + htb Abraham van der Merwe
2004-06-18 9:40 ` Ed Wildgoose
2004-06-18 11:12 ` pljosh
2004-06-19 20:36 ` 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=200406192236.11972.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