From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB burst, cburst parameters
Date: Mon, 10 Dec 2001 09:53:07 +0000 [thread overview]
Message-ID: <marc-lartc-100797806803724@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100794666623001@msgid-missing>
On Mon, 10 Dec 2001, Stef Coene wrote:
> > Not really.
> >
> > It kills all the traffic...giving me very low thruput....i read on the HTB
> > homepage that on x86 machines burst has to be a minimum of 12K or
> > something like that.
> >
> > Whats cburst ?
> If you set cbust equal to packet size, the rate will be checked each time you
> send cbust bytes and thus each time you send a packet. This would be ideal
> and you will never get a bust that exceed the ceil. Default cburst = 2Kb/8.
>
> But how do you get a burst? That's why you have the burst parameter. Each
> time you can poll the hardware, you can change to a new class. Devik
> calculated the burst for a i386 on a 10mbit and it's 12kb. So, you can send
> 12kb, choose an other class, send an other one, choose an other class.
> That's the fastest way you can work. The 12kb is sended as fast as possible
> and creates a burst. But with the cburst parameter you can control that
> burst. If you specify a bigger burst parameter, you can create bigger burst,
> but unload the CPU/hardware.
>
> I hope I'm explained it right. Devik ?
Almost :) The part "send 12k and select other class" is not exact.
Other class is selected also when current one is empty or DRR allotment
is exceeded.
Also cburst is not meant for burst reshaping (like peakrate in tbf)
but can be used for it.
tbf estimators always needs two parameters, rate and burst. There are
two estimators (rate and ceil) thus we have four (2*2) parameters:
rate/burst
ceil/cburst
I'm working on new patch to tc where you have not need to set
bursts. There are automaticaly computed from rate and ceil to
their smallest possible values (but you can still override them).
devik
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2001-12-10 9:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 0:27 [LARTC] HTB burst, cburst parameters Amit Kucheria
2001-12-10 7:03 ` Stef Coene
2001-12-10 7:08 ` Amit Kucheria
2001-12-10 7:56 ` Stef Coene
2001-12-10 7:58 ` Stef Coene
2001-12-10 9:53 ` Martin Devera [this message]
2001-12-10 20:31 ` Amit Kucheria
2001-12-11 10:01 ` devik
2001-12-11 18:39 ` Amit Kucheria
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-100797806803724@msgid-missing \
--to=devik@cdi.cz \
--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.