linux-kernel - Re: When did High-Resolution Timers hit mainline?

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: <alpine.LFD.1.10.0806250900240.3297@apollo.tec.linutronix.de>
Date:	Wed, 25 Jun 2008 09:09:39 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Michael Kerrisk <mtk.manpages@...glemail.com>
cc:	Ingo Molnar <mingo@...e.hu>, lkml <linux-kernel@...r.kernel.org>,
	Roman Zippel <zippel@...ux-m68k.org>,
	john stultz <johnstul@...ibm.com>
Subject: Re: When did High-Resolution Timers hit mainline?

On Wed, 25 Jun 2008, Michael Kerrisk wrote:
>    High-Resolution Timers
>        Before  Linux  2.6.16,  the  accuracy of timer and sleep system
>        calls (see below) was also limited by the size of the jiffy.
> 
>        Since  Linux  2.6.16,  Linux  supports  high-resolution  timers
>        (HRTs),  optionally  configurable  since kernel 2.6.21 via CON-
>        FIG_HIGH_RES_TIMERS.  On a system that supports HRTs, the accu-
>        racy  of  sleep and timer system calls is no longer constrained
>        by the jiffy, but instead can be as accurate  as  the  hardware
>        allows (microsecond accuracy is typical of modern hardware).

Hmm, that's a bit backwards. We changed the internal handling of those
interfaces to hrtimers in 2.6.16, but the accuracy is still jiffies
unless you have CONFIG_HIGH_RES_TIMERS enabled (which is only possible
as of 2.6.21) and your system provides the necessary hardware.
 
>        HRTs are not supported on all hardware architectures.  (Support
>        is provided on x86, arm, and powerpc, among others.)

Also you might point out that you can check whether high resolution
timers are active via clock_getres() or by checking the resolution
entry in /proc/timer_list.

Thanks,

	tglx

--
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/