From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB prio question
Date: Mon, 30 Jan 2006 15:22:41 +0000 [thread overview]
Message-ID: <20060130152241.GA16864@EIS> (raw)
In-Reply-To: <d82fbdb704081806045bc37031@mail.gmail.com>
On Mon, Jan 30, 2006 at 02:35:36PM +0200, Anton Glinkov wrote:
> Is the prio specification in the htb class global or is it on a per class
> basis? A simple example:
>
> class 1:10 parent 1:
> class 1:130 parent 1:10 prio 3
>
> class 1:170 parent 1:10 prio 7
> class 1:171 parent 1:170 prio 1
> class 1:172 parent 1:170 prio 2
>
> Which class will get excessive bandwidth first? 130 or 171/172?
I haven't tested it, but from my understanding, it should be 1:130.
Children classes should not be able to borrow from the outside
by themselves - they can only tell their parent to borrow for
them, so it's 1:130 (prio 3) vs 1:170 (prio 7) here.
Regards
Andreas Klauer
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-01-30 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 13:04 [LARTC] HTB prio question Michael Eck
2006-01-30 12:35 ` Anton Glinkov
2006-01-30 15:22 ` Andreas Klauer [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=20060130152241.GA16864@EIS \
--to=andreas.klauer@metamorpher.de \
--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.