From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] R2Q and more
Date: Mon, 29 Mar 2004 09:23:17 +0000 [thread overview]
Message-ID: <200403291123.17102.stef.coene@docum.org> (raw)
In-Reply-To: <20040324161622.2266F4014@outpost.ds9a.nl>
On Monday 29 March 2004 01:44, Roy wrote:
> > > Q2. What happens if the SUM of all the clients' class RATE
> (+
> > the
> >
> > > default class RATE) is bigger than 256kbit? Will HTB
>
> work
>
> > correctly?
> > Yes.
> > --------
> > This is incorrect:
> > of course it will work more or less, but nearly same as without
>
> any shaping
> It will work more then you think. On the short term, traffic can be bursty
> for the different classes, but each one will belimited to 8kbit. But on
> the long term, each class will get the same share of bandwidth.
> ------
> basicaly this may work if difference is not big,
There is one thing I learned: each setup and problem requires a different
aproaches. Sometimes, you can shape without being the bottlenek, sometimes
you can"t.
> but it was not working for me, I was trying to set rate 8kbit for everyone,
> since the sum of rates was 3 times biger than parent ceil, trafic was
> divided in unpredictable way.
> then I set rate to 1 kbit and everything worked well filling syslog by
> warnings that quantum is too small.
>
> logicaly this should not work because htb guarantee the rate amount trafic,
> so what if there is not so much available?
I 'm afraid the answer depends also on the client. The client that pushes the
most, will get the most.
> I'm not sure but, isn't quanum only used for leaf classes? So the quantum
> of
> parent classes doesn't mather ?
> ---------
> You may be right, since I did not checked source code for this, but
> logicaly quantum is very significant part
> and shoud work everywhere, I suppose quantum is about same as cburst, but
> even more significant,
> sems it is only way to divide bandwitch between classes with some
> proportion.
Quantum is only used if each child class is sending the configured rate and
the parent class has some bandwidth left. So if sum (rate of child classes)
= parent rate, quantum is never used. The class with the lowest prio will
get the remaining bandwidth, so the configured rate is the minimum rate of a
class.
> -----------------
> I found strange limitation, if class have leafs, then I cant attach sfq to
> it.
You can, but it will never be used.
> where will go unclasified packets from that class? Into root's default?
In previous versions, it hangs your system. I think the packets are send in
the :0 class, this is a passthru class.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.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:[~2004-03-29 9:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 15:46 [LARTC] R2Q and more Mihai Vlad
2004-03-28 17:50 ` Stef Coene
2004-03-28 19:18 ` Roy
2004-03-28 21:05 ` Stef Coene
2004-03-28 23:44 ` Roy
2004-03-29 6:55 ` Mihai Vlad
2004-03-29 9:23 ` Stef Coene [this message]
2004-03-29 15:11 ` Roy
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=200403291123.17102.stef.coene@docum.org \
--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.