All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: "Davda, Bhavesh P \(Bhavesh\)" <bhavesh@avaya.com>
Cc: Chris Friesen <cfriesen@nortel.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.11 timeval_to_jiffies() wrong for ms resolution timers
Date: Wed, 25 May 2005 13:02:14 -0700	[thread overview]
Message-ID: <4294D9C6.3060501@mvista.com> (raw)
In-Reply-To: <21FFE0795C0F654FAD783094A9AE1DFC07AFE7C1@cof110avexu4.global.avaya.com>

~
> On a more serious note: what is a real-time (read SCHED_FIFO/SCHED_RR) task to use to get millisecond accuracy wakeup timing services from the kernel? i.e. what are the alternatives to setitimer() that wake up the task exactly at the interval that is requested of it? You mention high-res timers as a possibility, but in the form of a patch. What's available in mainline unpatched?
> 
We ARE trying to get this into the main line, but save the patch, there is no 
way to get millisecond accuracy in the kernel OR in user land.  Never has been! 
  That is why the patch exists.  There was an effort by some university folks 
prior to the HRT stuff, but AFAIK it is not supported or uptodate.

Also, you should be aware that even with precise timers, there is still latency 
in the kernel AND it is in the millisecond range.  Again, folks are working on 
that in the form of a patch (see the the real time patch by Ingo and friends).

As for jiffies vs time, my understanding from senior time folks is that 1/HZ as 
a resolution is just an approximation.  We do the best we can but the x86 is 
really the PITs (pun intended) when it comes to time keeping resources.  If you 
really want millisecond accuracy, you may need to consider another platform....

-- 
George Anzinger   george@mvista.com
HRT (High-res-timers):  http://sourceforge.net/projects/high-res-timers/

  reply	other threads:[~2005-05-25 20:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-25 19:06 2.6.11 timeval_to_jiffies() wrong for ms resolution timers Davda, Bhavesh P (Bhavesh)
2005-05-25 20:02 ` George Anzinger [this message]
2005-05-25 21:41   ` Thomas Gleixner
2005-05-26 17:04   ` Olivier Croquette
2005-05-26 18:10     ` Richard B. Johnson
2005-05-26 18:19       ` Lee Revell
2005-05-26 19:24         ` George Anzinger
2005-05-26 19:32           ` Lee Revell
  -- strict thread matches above, loose matches on Subject: below --
2005-05-25 19:16 Davda, Bhavesh P (Bhavesh)
2005-05-24 22:59 Bhavesh P. Davda
2005-05-25 17:21 ` George Anzinger
2005-05-25 17:37   ` Chris Friesen
2005-05-25 17:54     ` George Anzinger
2005-05-25 18:07       ` Chris Friesen

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=4294D9C6.3060501@mvista.com \
    --to=george@mvista.com \
    --cc=bhavesh@avaya.com \
    --cc=cfriesen@nortel.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.