From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] negative tokens
Date: Thu, 27 Jan 2005 08:24:47 +0000 [thread overview]
Message-ID: <200501270924.48056.stef.coene@docum.org> (raw)
In-Reply-To: <3cfad9ca0501262342794e99e4@mail.gmail.com>
On Thursday 27 January 2005 08:42, Denis Kot wrote:
> I have this:
> class htb 1:29 parent 1:1 prio 0 rate 3000bit ceil 100000bit burst
> 1599b cburst 1611b
> Sent 33233 bytes 772 pkts (dropped 0, overlimits 0)
> lended: 415 borrowed: 357 giants: 0
> tokens: -3756376 ctokens: 128779
>
> or this:
> class htb 1:21 parent 1:1 prio 0 rate 3000bit ceil 100000bit burst
> 1599b cburst 1611b
> Sent 57554 bytes 618 pkts (dropped 0, overlimits 0)
> lended: 193 borrowed: 425 giants: 0
> tokens: -484950 ctokens: 128779
>
> and there is more like this
> what´s wrong?
Nothing.
To understand what's going on, I need the tc commands you use to create the
htb classes.
> this is class for imq0 device (for me this is ingres device) and I have
> this: imq0 Link encap:UNSPEC HWaddr
> 00-00-00-FF-FF-00-00-00-00-00-00-00-00-00-00-00
> UP RUNNING NOARP MTU:1500 Metric:1
> RX packets:131111 errors:0 dropped:0 overruns:0 frame:0
> TX packets:123371 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:30
> RX bytes:17694200 (16.8 Mb) TX bytes:15230834 (14.5 Mb)
>
> as you can see RX bytes doesn´t equal to TX bytes. what´s wrong?
That means that some packets are dropped because you shape on that interface.
Stef
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2005-01-27 8:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 7:42 [LARTC] negative tokens Denis Kot
2005-01-27 8:24 ` Stef Coene [this message]
2005-01-27 20:19 ` Denis Kot
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=200501270924.48056.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox