linux-kernel - Re: clock_getres() and real resolution

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:	Thu, 9 Feb 2012 06:12:18 +0100
From:	Richard Cochran <richardcochran@...il.com>
To:	Dmitry Antipov <dmitry.antipov@...aro.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	John Stultz <john.stultz@...aro.org>,
	linux-kernel@...r.kernel.org, linaro-dev@...ts.linaro.org
Subject: Re: clock_getres() and real resolution

On Wed, Feb 08, 2012 at 08:31:03AM -0800, Dmitry Antipov wrote:
> IIUC, an idea behind clock_getres() is to give a hint about the resolution of
> specified clock. This hint may be used by an application programmer to check whether
> this clock is suitable for a some purpose. So why clock_getres() always returns
> something like {0, 1} (if hrtimers are enabled) regardless of the underlying platform's
> real numbers?

I think "resolution" does not mean tick duration, but rather the finest timer unit.

HTH,
Richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/