From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB statistics
Date: Tue, 22 Mar 2005 21:41:03 +0000 [thread overview]
Message-ID: <424090EF.4060008@dsl.pipex.com> (raw)
In-Reply-To: <marc-lartc-105029768911081@msgid-missing>
m.innocenti@cineca.it wrote:
> Andy Furniss wrote:
>
>>> there is something I'm not able to understand about HTB statistics.
>>> Why the qdisc show show how many packets are overlimits but in the
>>> classes there are always 0 packets overlimits or dropped?
>>
>> Overlimits is more a kernel thing then usefull as a traffic control
>> figure and tc qdisc -s .. shows the root 1: htb but tc -s class doesn't.
>> You can see drops with tc -s class - but the default htb queue is too
>> long in this test. Add a specific queue to the class 1:10 so you can
>> specify length. eg.
>> tc qdisc add dev eth0 parent 1:10 handle 10: bfifo limit 64k
>
>
> Thank you for your reply. So there is not a way to know that a specific
> class is actually shaping the traffic without attaching a qdisc to each
> class?
>
>
Well the fact you are backlogged shows queue length - just default
length htb uses in this test is so long it doesn't drop.
If you had more classes they would be shorter and drop.
Adding a queue just lets you choose length - you won't really see any
better stats though you see more with tc -s qdisc.
You can also use tc -s class and look at the borrowed/lended counts and
see what you can deduce from those.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-03-22 21:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 5:31 [LARTC] HTB statistics maitri
2003-04-14 8:48 ` Stef Coene
2005-03-11 8:18 ` m.innocenti
2005-03-19 11:47 ` Andy Furniss
2005-03-21 8:24 ` m.innocenti
2005-03-22 1:34 ` rsenykoff
2005-03-22 21:41 ` Andy Furniss [this message]
2007-10-01 14:30 ` [LARTC] htb statistics Gerrit Brehmer
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=424090EF.4060008@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--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.