Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HFSC and default qdisc backlog
Date: Wed, 22 Mar 2006 00:03:25 +0000	[thread overview]
Message-ID: <4420944D.60101@trash.net> (raw)
In-Reply-To: <033e01c64d41$fd1ae8d0$1414a8c0@provsol.int>

James Nelson wrote:
> I don't understand the following:
>  
> root@jmnrouter:~# tc -s class ls dev vlan1 && tc -s qdisc ls 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: sc m1 0bit d 0us m2 220000bit ul m1 0bit d 0us m2
> 220000bit
>  Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
>  period 31304 work 7533852 bytes level 1
>  
> class hfsc 1:10 parent 1:1 sc m1 1024bit d 8.0ms m2 100000bit ul m1 0bit d
> 0us m2 220000bit
>  Sent 6892869 bytes 33300 pkts (dropped 0, overlimits 0)
>  period 32750 work 6892869 bytes rtwork 6725586 bytes level 0
>  
> class hfsc 1:20 parent 1:1 sc m1 4096bit d 100.0ms m2 75000bit ul m1 0bit d
> 0us m2 220000bit
>  Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
>  period 0 level 0
>  
> class hfsc 1:30 parent 1:1 sc m1 8200bit d 200.0ms m2 30000bit ul m1 0bit d
> 0us m2 220000bit
>  Sent 640821 bytes 636 pkts (dropped 0, overlimits 0)
>  period 277 work 640821 bytes rtwork 199829 bytes level 0
>  
> class hfsc 1:40 parent 1:1 sc m1 8200bit d 300.0ms m2 15008bit ul m1 0bit d
> 0us m2 220000bit
>  Sent 162 bytes 3 pkts (dropped 0, overlimits 0)
>  period 3 work 162 bytes rtwork 162 bytes level 0
>  
> qdisc hfsc 1: default 30
>  Sent 7537524 bytes 33953 pkts (dropped 6, overlimits 4145)
>  backlog 3p
> 
>  
> Why is the qdisc backloged with dropped packets and overlimits when the
> classes are not?

You seen to be using an old iproute version. There was some
compatibility breakage that affected statistics.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2006-03-22  0:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-21 23:48 [LARTC] HFSC and default qdisc backlog James Nelson
2006-03-22  0:03 ` Patrick McHardy [this message]
2006-03-23  0:13 ` James Nelson
2006-03-23  0:27 ` Jason Boxman
2006-03-23  4:03 ` Patrick McHardy
2006-04-12 15:04 ` Andy Furniss

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=4420944D.60101@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox