From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB and theory
Date: Mon, 09 Dec 2002 21:22:08 +0000 [thread overview]
Message-ID: <marc-lartc-103946902510261@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103945416224487@msgid-missing>
> | rate of parent .... You don't have to follow this rules, but the final
> | shaping result can be strange.
> | See the faq page on www.docum.org.
>
> I've already seen it :-) But it doesn't say anything like:
> sum (child ceils) <= ceil of parent
> Is there such a rule?
Yes : child ceil <= ceil of parent (I just added it to the faq page)
> Am I forced somehow to limit 'rate' of class 11:2 under the guaranteed
> value (5000Kbit), but let the 'ceil' equal to this value? It's better to
> give the clients let's say 95% of guaranteed bandwidth instead of 100%?
You can argument that limit a client to 95% will leave 5% for someone else.
But I think 100% is a better choice.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-12-09 21:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 17:14 [LARTC] HTB and theory Catalin Bucur
2002-12-09 18:22 ` Stef Coene
2002-12-09 20:27 ` Catalin Bucur
2002-12-09 21:22 ` Stef Coene [this message]
2002-12-09 21:45 ` Catalin Bucur
2002-12-09 22:18 ` Abraham van der Merwe
2002-12-10 12:33 ` Stef Coene
2002-12-10 12:40 ` Stef Coene
2002-12-10 13:28 ` Abraham van der Merwe
2002-12-10 21:23 ` Stef Coene
2002-12-12 8:36 ` Abraham van der Merwe
2002-12-12 10:49 ` Stef Coene
2002-12-12 11:19 ` Abraham van der Merwe
2002-12-12 18:32 ` 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-103946902510261@msgid-missing \
--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