netdev - Re: [BUG #12364] Re: HTB - very bad precision? HFSC works fine! 2.6.28

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]

Message-ID: <496C541E.6080203@ziu.info>
Date:	Tue, 13 Jan 2009 09:43:10 +0100
From:	Michal Soltys <soltys@....info>
To:	Stephen Hemminger <shemminger@...tta.com>
CC:	Patrick McHardy <kaber@...sh.net>,
	Denys Fedoryschenko <denys@...p.net.lb>,
	Jesper Dangaard Brouer <hawk@...u.dk>,
	netdev <netdev@...r.kernel.org>, bugme-daemon@...zilla.kernel.org
Subject: Re: [BUG #12364] Re: HTB - very bad precision? HFSC works fine! 2.6.28

Stephen Hemminger wrote:
> On Tue, 13 Jan 2009 05:33:14 +0100
> 
> Even with NO_HZ the regular kernel won't schedule timers sooner
> than HZ. I believe it caused regressions so it was disabled.

While making manpage(s) for hfsc (I'll post it soon), I've done some 
tests - setting trivial hfsc class, essentially as a tbf emulator, 
produces impressive amount of timer interrupts.

tc qdisc add dev eth0 root handle 1:0 hfsc default 1
tc class add dev eth0 parent 1:0 classid 1:1 hfsc rt m2 300mbit

nc -u dst.host.com 54321 </dev/zero
nc -l -p 54321 >/dev/null

319: 42124229   0  HPET_MSI-edge  hpet2 (before)
319: 42436214   0  HPET_MSI-edge  hpet2 (after ~10s.)

That's over 30,000 per second. CPU load is another thing in this case 
(still easily tolerable by cheap dual core amd cpu), but interrupt rate 
goes easily far beyond HZ mark. Of course both 'tickless system' and 'hr 
timers' must be enabled.
--
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