From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] hfsc and dropped packets
Date: Tue, 14 Mar 2006 00:03:24 +0000 [thread overview]
Message-ID: <4416084C.5080902@trash.net> (raw)
In-Reply-To: <086101c646eb$5e4ab110$1414a8c0@provsol.int>
Patrick McHardy wrote:
> James Nelson wrote:
>
>>root@jmnrouter:/jmn# tc class show dev vlan1
>> [...]
>>
>>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.
BTW, in your case the drops most likely occur because HFSC's default
pfifo child qdiscs use the tx_queue_len of the device as their limit,
which in case of vlan devices is zero (in that case 1 is used).
So you can either increase the tx_queue_len of the vlan device
or manually add child qdiscs with bigger limits.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-03-14 0:03 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
2006-03-14 0:03 ` Patrick McHardy [this message]
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=4416084C.5080902@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.