netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Denys Fedoryschenko <denys@visp.net.lb>
Cc: netdev@vger.kernel.org
Subject: Re: HTB vs HFSC, HTB is highly inaccurate
Date: Mon, 9 Mar 2009 08:07:00 +0000	[thread overview]
Message-ID: <20090309080700.GA4760@ff.dom.local> (raw)
In-Reply-To: <200903082045.39083.denys@visp.net.lb>

On 08-03-2009 19:45, Denys Fedoryschenko wrote:
> Hi again
> 
> I test again HTB and HFSC, this time in very simple case.
> 
> Regarding HTB - i try without quantum, with different values, without and with 
> cburst (big and small), with HZ=1000 and default, hysteresis on and off - it 
> is almost same result. 
> 
> While i set limit at 57, it can reach 61. HFSC results is perfect.
> 
> Here is graph snapshopts.
> http://www.nuclearcat.com/netdev/htb-problem.png
> You can see points where HTB enabled. Other points if HFSC.

Very nice picture, but some tc snapshot stats for qdisc and classes
would be appreciated.

> 
> Scripts source is:
> 
> HTB http://www.nuclearcat.com/netdev/htb-script.txt

| echo "class add dev eth0.37 parent 1:1 classid 1:2 htb rate 40Mbit ceil 56Mbit burst 16000b cburst 16000b quantum 16000"
| echo "class add dev eth0.37 parent 1:1 classid 1:3 htb rate 26Mbit ceil 56Mbit burst 16000b cburst 16000b quantum 16000"

I guess you should try with rates 40/16 or 30/26 here.

BTW, it doesn't matter here, but for various reasons it's better to
add classes before filters pointing these classes.

> HFSC http://www.nuclearcat.com/netdev/hfsc-script.txt

This link doesn't work for me.

Jarek P.

  reply	other threads:[~2009-03-09  8:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-08 18:45 HTB vs HFSC, HTB is highly inaccurate Denys Fedoryschenko
2009-03-09  8:07 ` Jarek Poplawski [this message]
2009-03-09  8:18   ` Denys Fedoryschenko

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=20090309080700.GA4760@ff.dom.local \
    --to=jarkao2@gmail.com \
    --cc=denys@visp.net.lb \
    --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).