public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: greg <ustrel@free.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Clock resolution / RT preemption
Date: Mon, 01 Aug 2005 16:28:04 -0700	[thread overview]
Message-ID: <42EEB004.4040601@mvista.com> (raw)
In-Reply-To: <42EDD473.3010308@free.fr>

greg wrote:
> Hi folks,
> 
> I'm looking for a timer resolution lower than 1 ms (and monotonic clock 
> rate) destined to be used with some network code running on x86 
> platforms. Would you please provide me with informations about how to 
> get/implement this.
> 
> AFAIK, there's a "high resultion timer" patch hanging around, but 
> there's not much informations with regard to portability (specific 
> hardware requirements ?), scalability, integration with RT patches.
> I understand the POSIX 1003.1b Clocks and Timers system calls are not 
> fully available within the linux kernel (and libc ?), am I right on that ?

On the HRT web site (see signature) there is a CVS repository.  In there 
is a special version for the RT kernel.  As to porting it to other 
archs, have a look at the include/linux/hrtimer.h file.  It has (or 
should have) all you need to know.  Please pass back any port you do.
> 
> One more question : I believe Ingo's preemption patch run 
> timers/interrupt handlers within kernel threads, how should I assign 
> specific priority to address my goals without compromising system 
> stability ?

Carefully :)

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

      reply	other threads:[~2005-08-01 23:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-01  7:51 Clock resolution / RT preemption greg
2005-08-01 23:28 ` George Anzinger [this message]

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=42EEB004.4040601@mvista.com \
    --to=george@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ustrel@free.fr \
    /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