From: Daniel Frederiksen <cyberdoc@cyberdoc.dk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Excess Bandwidth
Date: Sat, 09 Oct 2004 01:45:29 +0000 [thread overview]
Message-ID: <1097286328.20741.7.camel@hermes> (raw)
In-Reply-To: <4166FA94.2090208@cyclades.com.br>
Hej Ronaldo
Remember to prioritize the excess bandwidth. If you are using the HTB
read the bottom section of the manual.:
http://luxik.cdi.cz/~devik/qos/htb/manual/userg.htm#prio
The "prio" parameter will help you with your problem, give the child
classes a priority from 1-3, where 1 is the highest priority and 3 is
the lowest.
On Fri, 2004-10-08 at 22:37, Ronaldo Z. Afonso wrote:
> Hi,
>
> I'm trying to configure QoS on my linux in the following manner:
> I have a main link with 64K, so I divided it in 3 classes of 18K, 14K
> and 9K with an excess (not used for classified traffic, just to be
> shared) of 23K. This excess should be distributed proportonally among
> the 3 classes, that is, the class that has more rate should borrow more
> bandwidth. What is happening is just the opposite, the class that has
> less rate is borrowing more bandwidth. A representation of my
> "hierarchical class layout" is as follow:
>
> root - 64K
>
> A - 18K B - 14K C - 9K
>
> I have read some documentation that says it should work exactly in
> this in way, but it is not happening in my environment. All the tests I
> did show me that the class with less rate is borrow more bandwidth.
> Can anyone help me?
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-10-09 1:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 20:37 [LARTC] Excess Bandwidth Ronaldo Z. Afonso
2004-10-09 1:45 ` Daniel Frederiksen [this message]
2004-10-14 8:14 ` Ronaldo Z. Afonso
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=1097286328.20741.7.camel@hermes \
--to=cyberdoc@cyberdoc.dk \
--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