mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "Thomas Gleixner" <tglx@linutronix.de>, "Ingo Molnar" <mingo@elte.hu>
Cc: lkml <linux-kernel@vger.kernel.org>,
	"Roman Zippel" <zippel@linux-m68k.org>,
	"john stultz" <johnstul@us.ibm.com>
Subject: When did High-Resolution Timers hit mainline?
Date: Tue, 24 Jun 2008 08:35:11 +0200	[thread overview]
Message-ID: <cfd18e0f0806232335p3e05d690o5a5cef8c9626fae7@mail.gmail.com> (raw)

Hi Ingo, Thomas,

I want to update some timer and sleep man pages to reflect the arrival
of high-resolution timers.  However, it's not quite clear to me when
HRTs properly arrived in mainline.  Was it 2.6.21?  And at that point,
was the resolution for all timer and sleep calls based on HRTs, so
that they all became more accurate?  (Or was it the case that various
system calls switched over to HRTs in different later kernel
versions?)  Specifically, I'm thinking of the following system calls

nanosleep()
clock_nanosleep()
setitimer()
timer_create()/timer_settime()

Was it the case that pre 2.6.21 (or whatever) these were all
jiffy-based in their accuracy, and then post 2.6.21, they were all HRT
based (if CONFIG_HIGH_RES_TIMERS is enabled)?

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

             reply	other threads:[~2008-06-24  6:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24  6:35 Michael Kerrisk [this message]
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
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=cfd18e0f0806232335p3e05d690o5a5cef8c9626fae7@mail.gmail.com \
    --to=mtk.manpages@googlemail.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®