From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Over value in CEIL parameter..
Date: Wed, 23 Jul 2003 14:16:29 +0000 [thread overview]
Message-ID: <marc-lartc-105896988320550@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105893713024294@msgid-missing>
On Wednesday 23 July 2003 07:40, Martin A. Brown wrote:
> Hello again Rio Martin,
>
> : I ve set CEIL parameter each class not more than 128Kbit But sometimes
> : the CEIL parameter can be higher 128Kbit As far as i monitored, this
> : CEIL rate can be 132Kbit maximum, dont know why..
>
> For how long does the monitored output traffic exceed your ceiling? It is
> possible that you'll exceed your ceil briefly because the allotted traffic
> can exceed ceiling by the amount of cburst.
>
> If you are recording an output rate above your ceil (128kbit) consistently
> over a long period of time (a large transfer), then I, also, do not know
> why.
>
> [ Stef may have more to say about this. ]
132kbit - 128kbit = 4kbit and that's not much. So I don't think you have to
worry.
Is this ceil parameter on a leaf class (a class with no child classes)? Or
can you post you script?
Also, execute tc -s -d clas sshow dev eth0 and watch the ctokens. They should
never be negative for that 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/
next prev parent reply other threads:[~2003-07-23 14:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 5:14 [LARTC] Over value in CEIL parameter Rio Martin.
2003-07-23 5:40 ` Martin A. Brown
2003-07-23 6:53 ` Rio Martin.
2003-07-23 14:16 ` Stef Coene [this message]
2003-07-24 2:22 ` Rio Martin.
2003-07-24 16:28 ` Stef Coene
2003-07-29 5:28 ` Rio Martin.
2003-07-29 7:45 ` 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-105896988320550@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