netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antonio Almeida <vexwek@gmail.com>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: netdev@vger.kernel.org, kaber@trash.net, davem@davemloft.net,
	devik@cdi.cz
Subject: Re: HTB - What's the minimal value for 'rate' parameter?
Date: Wed, 14 Apr 2010 11:22:26 +0100	[thread overview]
Message-ID: <p2q298f5c051004140322hc54f5315taa5c7d85cb74f06@mail.gmail.com> (raw)
In-Reply-To: <20100409212657.GA3560@del.dom.local>

What do you mean with "1:2 has grandchildren with overflown rate tables"?
I couldn't understand your idea. Is there any mistake in the
configuration I sent?
How would you set rates for this particular example?

Regards
  Antonio Almeida



On Fri, Apr 9, 2010 at 10:26 PM, Jarek Poplawski wrote:
> On Fri, Apr 09, 2010 at 04:40:44PM +0100, Antonio Almeida wrote:
>> So, what about the rate limit miss?
>> As you can see the ceil of class 1:2 is set to 4096Kbit but its
>> sending rate is actually 8071Kbit!
>> It looks like classes 1:10 and 1:11 are ignoring hierarchical rate
>> restrictions of class 1:2
>> Here:
>> class htb 1:2 parent 1:1 rate 4096Kbit ceil 4096Kbit burst 3655b cburst 3655b
>>  Sent 84285894 bytes 55671 pkt (dropped 0, overlimits 0 requeues 0)
>>  rate 8071Kbit 666pps backlog 0b 0p requeues 0
>>  lended: 0 borrowed: 0 giants: 0
>>  tokens: -937499999 ctokens: -937499999
>
> Yes, since 1:2 has grandchildren with overflown rate tables, they
> could behave as if they had set rates higher than their parents or
> grandparent (and HTB doesn't restrict it hierarchically).
>
> Jarek P.
>

  reply	other threads:[~2010-04-14 10:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08 11:07 HTB - What's the minimal value for 'rate' parameter? Antonio Almeida
2010-04-08 21:33 ` Jarek Poplawski
2010-04-09 15:40   ` Antonio Almeida
2010-04-09 21:26     ` Jarek Poplawski
2010-04-14 10:22       ` Antonio Almeida [this message]
2010-04-14 21:45         ` Jarek Poplawski
2010-04-16 11:56           ` Antonio Almeida
2010-04-17  9:19           ` Benny Amorsen
2010-04-17 21:01             ` Jarek Poplawski

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=p2q298f5c051004140322hc54f5315taa5c7d85cb74f06@mail.gmail.com \
    --to=vexwek@gmail.com \
    --cc=davem@davemloft.net \
    --cc=devik@cdi.cz \
    --cc=jarkao2@gmail.com \
    --cc=kaber@trash.net \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).