mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Michael Kerrisk <mtk.manpages@googlemail.com>
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:22:32 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.1.10.0806251421580.3297@apollo.tec.linutronix.de> (raw)
In-Reply-To: <cfd18e0f0806250520u565d512as298f024df06da857@mail.gmail.com>

On Wed, 25 Jun 2008, Michael Kerrisk wrote:
> > 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?

Make this 2.6.21 :)

Thanks,
	tglx

  reply	other threads:[~2008-06-25 12:26 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
2008-06-25 12:22       ` Thomas Gleixner [this message]
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=alpine.LFD.1.10.0806251421580.3297@apollo.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=bart.vanassche@gmail.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mtk.manpages@googlemail.com \
    --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®