netdev - Re: HTB vs HFSC, HTB is highly inaccurate

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 9 Mar 2009 08:07:00 +0000
From:	Jarek Poplawski <jarkao2@...il.com>
To:	Denys Fedoryschenko <denys@...p.net.lb>
Cc:	netdev@...r.kernel.org
Subject: Re: HTB vs HFSC, HTB is highly inaccurate

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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html