From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] overlimits value in statistics
Date: Sun, 08 Sep 2002 09:57:43 +0000 [thread overview]
Message-ID: <marc-lartc-103147913329479@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103145991522910@msgid-missing>
On Sunday 08 September 2002 06:43, Igor Suvorov wrote:
> Good Day!
>
> I was interested with a question what exactly
> is considered in overlimits parameter to count
> of statistics. I thought, that this parameter
> should specify number of the packages which
> have exceeded valid boundary. But, for example
> statistics on one of queues:
I have some more info on www.docum.org (FAQ page) :
overlimits : Packet is not sended due to ceil or rate restrictions
So there was to much data in the class. But don't believe this too much. It
depends on how often the qdisc looked for packet. This counter is incremented
per unsucessfull DRR loop and it's possible that this happens more then once
per packet.
Each dropped packet is overlimited.
> class cbq 20:12 parent 20:10 leaf 8015: rate 128Kbit (bounded) prio 5
> Sent 23171746615 bytes 43153460 pkts (dropped 81179, overlimits 641814686)
> backlog 1p
>
> Queue has passed 43153460 packets, but has
> exceeded a valid level of 641814686 packets.
> What it? Errors?
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:[~2002-09-08 9:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-08 4:43 [LARTC] overlimits value in statistics Igor Suvorov
2002-09-08 9:57 ` Stef Coene [this message]
2002-09-08 12:07 ` Igor Suvorov
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-103147913329479@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.