netdev - Re: [PATCH 2/2] pkt_sched: Change PSCHED

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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 09 Jun 2009 05:21:29 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jarkao2@...il.com
Cc:	kaber@...sh.net, vexwek@...il.com, shemminger@...tta.com,
	netdev@...r.kernel.org, devik@....cz, dada1@...mosbay.com,
	hazard@...ncoudi.com, slavon@...telecom.ru
Subject: Re: [PATCH 2/2] pkt_sched: Change PSCHED_SHIFT from 10 to 6

From: Jarek Poplawski <jarkao2@...il.com>
Date: Tue, 9 Jun 2009 08:05:13 +0000

> Change PSCHED_SHIFT from 10 to 6 to increase schedulers time
> resolution. This will increase 16x a number of (internal) ticks per
> nanosecond, and is needed to improve accuracy of schedulers based on
> rate tables, like HTB, TBF or CBQ, with rates above 100Mbit. It is
> assumed this change is safe for 32bit accounting of time diffs up
> to 2 minutes, which should be enough for common use (extremely low
> rate values may overflow, so get inaccurate instead). To make full
> use of this change an updated iproute2 will be needed. (But using
> older iproute2 should be safe too.)
> 
> This change breaks ticks - microseconds similarity, so some minor code
> fixes might be needed. It is also planned to change naming adequately
> eg. to PSCHED_TICKS2NS() etc. in the near future.
> 
> Reported-by: Antonio Almeida <vexwek@...il.com>
> Tested-by: Antonio Almeida <vexwek@...il.com>
> Signed-off-by: Jarek Poplawski <jarkao2@...il.com>

Applied.
--
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