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: Thu, 19 May 2005 10:02:45 -0700 [thread overview]
Message-ID: <428CC6B5.3070206@mvista.com> (raw)
In-Reply-To: <m1hdh0yu14.fsf@muc.de>
Andi Kleen wrote:
~>
>
> If you do a new structure for this I would suggest adding a
> "precision" field (or the same with a different name). Basically
> precision would tell the kernel that the wakeup can be in a time
> range, not necessarily on the exact time specified. This helps
> optimizing the idle loop because you can batch timers better and is
> important for power management and virtualized environments. The
> kernel internally does not use support this yet, but there are plans
> to change the internal timers in this direction and if you're defining
> a new user interface I would add support for this.
>
> I am not sure precision would be the right name, other suggestions
> are welcome.
>
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.
>
~
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
next prev parent reply other threads:[~2005-05-19 17:03 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 [this message]
2005-05-19 18:35 ` Inaky Perez-Gonzalez
2005-05-20 19:05 ` Andi Kleen
2005-05-21 1:12 ` George Anzinger
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=428CC6B5.3070206@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.