From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "Thomas Gleixner" <tglx@linutronix.de>
Cc: "Ingo Molnar" <mingo@elte.hu>,
lkml <linux-kernel@vger.kernel.org>,
"Roman Zippel" <zippel@linux-m68k.org>,
"john stultz" <johnstul@us.ibm.com>,
"Bart Van Assche" <bart.vanassche@gmail.com>
Subject: Re: When did High-Resolution Timers hit mainline?
Date: Wed, 25 Jun 2008 14:20:26 +0200 [thread overview]
Message-ID: <cfd18e0f0806250520u565d512as298f024df06da857@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0806250900240.3297@apollo.tec.linutronix.de>
Thomas,
On Wed, Jun 25, 2008 at 9:09 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> 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.
So then it's simply enough to say:
Since Linux 2.6.17, Linux optionaly supports high-resolution timers
(configurable via CONFIG_HIGH_RES_TIMERS).
right?
>> 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.
Okay -- thanks.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
next prev parent reply other threads:[~2008-06-25 12:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 6:35 Michael Kerrisk
2008-06-25 4:08 ` Michael Kerrisk
2008-06-25 6:32 ` Bart Van Assche
2008-06-25 12:16 ` Michael Kerrisk
2008-06-25 13:33 ` Michael Kerrisk
2008-06-25 14:11 ` Michael Kerrisk
2008-06-25 7:09 ` Thomas Gleixner
2008-06-25 12:20 ` Michael Kerrisk [this message]
2008-06-25 12:22 ` Thomas Gleixner
2008-06-25 12:25 ` Michael Kerrisk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cfd18e0f0806250520u565d512as298f024df06da857@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=bart.vanassche@gmail.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=zippel@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®