From: George Anzinger <george@mvista.com>
To: Andi Kleen <ak@muc.de>
Cc: joe.korty@ccur.com, robustmutexes@lists.osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] A more general timeout specification
Date: Fri, 20 May 2005 18:12:15 -0700 [thread overview]
Message-ID: <428E8AEF.9030609@mvista.com> (raw)
In-Reply-To: <20050520190550.GB57598@muc.de>
Andi Kleen wrote:
>>I think the accepted and standard way to do this is to use different
>>"clock"s. For example, in the HRT patch the clocks CLOCK_REALTIME_HR and
>>CLOCK_MONOTONIC_HR are defined as high resolution clocks.
>
>
> Note precision here can be fairly long - some timers dont even
> if they run a minute earlier or later or even longer. For others
> it can be rather small.
>
> I dont think you want own clocks for all possible numbers. It makes
> much more sense to give a numerical time offset.
That may be, but you will have a hard time finding a standard confroming way to
pass that info into the kernel. A few well chosen points should do it...
>
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
next prev parent reply other threads:[~2005-05-21 1:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 20:15 [RFC] A more general timeout specification Joe Korty
2005-05-18 22:15 ` Inaky Perez-Gonzalez
2005-05-19 13:39 ` Joe Korty
2005-05-18 23:49 ` Andi Kleen
2005-05-19 13:24 ` Joe Korty
2005-05-19 17:02 ` George Anzinger
2005-05-19 18:35 ` Inaky Perez-Gonzalez
2005-05-20 19:05 ` Andi Kleen
2005-05-21 1:12 ` George Anzinger [this message]
2005-07-29 1:52 ` FW: " Inaky Perez-Gonzalez
2005-08-22 22:56 ` john stultz
-- strict thread matches above, loose matches on Subject: below --
2005-09-01 0:00 Perez-Gonzalez, Inaky
2005-09-01 9:19 ` Roman Zippel
2005-09-01 13:48 ` Joe Korty
2005-09-01 15:18 ` Roman Zippel
2005-09-01 21:20 ` Kyle Moffett
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=428E8AEF.9030609@mvista.com \
--to=george@mvista.com \
--cc=ak@muc.de \
--cc=joe.korty@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robustmutexes@lists.osdl.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.