From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB equivalent for 'bounded' and 'isolated' in CBQ
Date: Thu, 29 Aug 2002 13:08:10 +0000 [thread overview]
Message-ID: <marc-lartc-103062738900487@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102953224700762@msgid-missing>
> It works fine for me, although I haven't used CBQ previously so I can't
> comapre them. It just works for me, except the delays in interactive class
> are too long, even when the prio is 0 (highest) and the rate and ceil are
> maximum. Maybe CBQ is better in reducing the delays... Anybody solved this
> problem?
There is a way with htb to get really low delays. It can be found on the htb
homepage (http://luxik.cdi.cz/~devik/qos/htb/manual/userg.htm#prio, last
paragraph).
Basically, you have 2 classes : on rated to xx% of the link and an other rated
to 100-X%. If you make sure you NEVER send more data to the 100-xx% class so
it never has to ask for more bandwidth, it will have very low delays. If you
send more data, the situation is reversed and that class will get very high
delays. I still have to test it, but you can use the policer in the filters
to make sure you never send more data then the rate of the class.
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/
prev parent reply other threads:[~2002-08-29 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-16 21:09 [LARTC] HTB equivalent for 'bounded' and 'isolated' in CBQ Amit Kucheria
2002-08-18 20:01 ` Stef Coene
2002-08-21 3:32 ` Amit Kucheria
2002-08-21 17:48 ` Stef Coene
2002-08-29 6:26 ` Radosław Łoboda
2002-08-29 13:08 ` 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=marc-lartc-103062738900487@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 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.