From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] hfsc and dropped packets
Date: Mon, 13 Mar 2006 23:53:09 +0000 [thread overview]
Message-ID: <441605E5.7080405@trash.net> (raw)
In-Reply-To: <086101c646eb$5e4ab110$1414a8c0@provsol.int>
James Nelson wrote:
> Hi,
>
> I'm trying to get a handle on hfsc. Here is my configuration:
>
> root@jmnrouter:/jmn# tc class show dev vlan1
> class hfsc 1: root
> class hfsc 1:1 parent 1: ls m1 0bit d 0us m2 225000bit ul m1 0bit d 0us m2
> 225000bit
> class hfsc 1:10 parent 1:1 rt m1 191000bit d 25.0ms m2 135000bit ls m1 0bit
> d 0us m2 135000bit ul m1 0bit d 0us m2 225000bit
> class hfsc 1:20 parent 1:1 rt m1 22008bit d 25.0ms m2 56008bit ls m1 0bit d
> 0us m2 56008bit ul m1 0bit d 0us m2 225000bit
> class hfsc 1:30 parent 1:1 rt m1 11008bit d 25.0ms m2 22008bit ls m1 0bit d
> 0us m2 22008bit ul m1 0bit d 0us m2 225000bit
> class hfsc 1:40 parent 1:1 rt m1 0bit d 25.0ms m2 11008bit ls m1 0bit d 0us
> m2 11008bit ul m1 0bit d 0us m2 225000bit
>
> And here is the stats right after I run the qos script with no load on the
> link(adsl):
> root@jmnrouter:/jmn# tc -s class show dev vlan1
> class hfsc 1: root
> Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
> period 0 level 2
>
> class hfsc 1:1 parent 1: ls m1 0bit d 0us m2 225000bit ul m1 0bit d 0us m2
> 225000bit
> Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
> period 349 work 42417 bytes level 1
>
> class hfsc 1:10 parent 1:1 rt m1 191000bit d 25.0ms m2 135000bit ls m1 0bit
> d 0us m2 135000bit ul m1 0bit d 0us m2 225000bit
> Sent 31297 bytes 304 pkts (dropped 18, overlimits 0)
> period 304 work 31297 bytes rtwork 30991 bytes level 0
>
> class hfsc 1:20 parent 1:1 rt m1 22008bit d 25.0ms m2 56008bit ls m1 0bit d
> 0us m2 56008bit ul m1 0bit d 0us m2 225000bit
> Sent 7302 bytes 17 pkts (dropped 2, overlimits 0)
> period 17 work 7302 bytes rtwork 7010 bytes level 0
>
> class hfsc 1:30 parent 1:1 rt m1 11008bit d 25.0ms m2 22008bit ls m1 0bit d
> 0us m2 22008bit ul m1 0bit d 0us m2 225000bit
> Sent 3818 bytes 28 pkts (dropped 0, overlimits 0)
> period 28 work 3818 bytes rtwork 3818 bytes level 0
>
> class hfsc 1:40 parent 1:1 rt m1 0bit d 25.0ms m2 11008bit ls m1 0bit d 0us
> m2 11008bit ul m1 0bit d 0us m2 225000bit
> Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
> period 0 level 0
>
>
> Why is there dropped packets but nothing overlimits??
Overlimits counts dequeue-attempts that were unsuccessful because of
qdisc limits. Drops usually occur when the inner qdisc is full during
enqueue, so they have quite opposite meanings.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-03-13 23:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 22:13 [LARTC] hfsc and dropped packets James Nelson
2006-03-13 23:53 ` Patrick McHardy [this message]
2006-03-14 0:03 ` Patrick McHardy
2006-03-14 0:39 ` James Nelson
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=441605E5.7080405@trash.net \
--to=kaber@trash.net \
--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.