From: Lars Landmark <larslan@solan.zapto.org>
To: lartc@vger.kernel.org
Subject: [LARTC] HTB question
Date: Sat, 28 Jun 2003 11:58:55 +0000 [thread overview]
Message-ID: <marc-lartc-105680159222430@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101819226308335@msgid-missing>
I have a question regarding how HTB choose to send a package when the rate
is almost reached.
What I would like to know, is how HTB solve this;
The class rate has not yet been reached. When htb now
dequeue the next package, rate would be crossed.
The next package is smaller than the quantum parameter.
Would HTB delay this package, or just send it?
If latter, then HTB is able to cross its configured class rate
without any borrowing.. Hence send at its full speed until
the bucket is emptied.
Does HTB has any bucket containing unused tokens like token bucket?
Or does HTB only accumulate tokens at its configured rate, while unused
token are dropped??
Thanks in advance
Lars
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-06-28 11:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-07 15:09 [LARTC] HTB question Omer suat
2002-04-07 15:17 ` Martin Devera
2002-04-07 15:21 ` Stef Coene
2002-05-13 17:30 ` Pavlos Parissis
2003-04-09 18:06 ` [LARTC] HTB Question Allan Gee
2003-05-23 9:56 ` [LARTC] HTB question Ruslan Spivak
2003-06-28 11:58 ` Lars Landmark [this message]
2003-06-28 16:09 ` Stoilis Giannis
2004-01-15 11:07 ` [LARTC] HTB Question hare ram
2006-09-13 14:47 ` [LARTC] HTB question doudouyam
-- strict thread matches above, loose matches on Subject: below --
2003-06-04 20:27 [LARTC] HTB Question TeraHz
2003-06-04 20:46 ` Stef Coene
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=marc-lartc-105680159222430@msgid-missing \
--to=larslan@solan.zapto.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 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.