From: George Anzinger <george@mvista.com>
To: Alex Williamson <alex.williamson@hp.com>
Cc: Christoph Lameter <clameter@engr.sgi.com>,
john stultz <johnstul@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: Need better is_better_time_interpolator() algorithm
Date: Fri, 26 Aug 2005 12:16:14 -0700 [thread overview]
Message-ID: <430F6A7E.203@mvista.com> (raw)
In-Reply-To: <1125073089.5182.30.camel@tdi>
Alex Williamson wrote:
> On Fri, 2005-08-26 at 08:39 -0700, Christoph Lameter wrote:
>
>
>>I think a priority is something useful for the interpolators. Some of
>>the decisions about which time sources to use also have criteria different
>>from drift/latency/jitter/cpu. F.e. timers may not survive various
>>power-saving configurations. Thus I would think that we need a priority
>>plus some flags.
>>
>>Some of the criteria for choosing a time source may be:
>
>
> Hi Christoph,
>
> I sent another followup to this thread with a patch containing a
> fairly crude algorithm that I think better explains my starting point.
> I'm sure the weighting and scaling factors need work, but I think many
> of the criteria you describe will favor the right clock.
>
>
>>1. If a system boots up with a single cpu then there is no question that
>>the ITC/TSC should be used because of the fast access.
We need to factor in frequency shifting here, especially if it happens
with out notice.
~
--
George Anzinger george@mvista.com
HRT (High-res-timers): http://sourceforge.net/projects/high-res-timers/
next prev parent reply other threads:[~2005-08-26 19:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 16:44 Need better is_better_time_interpolator() algorithm Alex Williamson
2005-08-25 17:36 ` john stultz
2005-08-25 18:43 ` Alex Williamson
2005-08-25 19:02 ` john stultz
2005-08-26 15:39 ` Christoph Lameter
2005-08-26 16:18 ` Alex Williamson
2005-08-26 19:16 ` George Anzinger [this message]
2005-08-26 19:26 ` Alex Williamson
2005-08-26 19:33 ` Christoph Lameter
2005-08-26 19:51 ` George Anzinger
2005-08-27 11:55 ` Pavel Machek
2005-08-29 17:00 ` Christoph Lameter
-- strict thread matches above, loose matches on Subject: below --
2005-08-25 21:40 linux
2005-08-25 23:07 ` Alex Williamson
2005-08-26 16:48 ` Christoph Lameter
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=430F6A7E.203@mvista.com \
--to=george@mvista.com \
--cc=alex.williamson@hp.com \
--cc=clameter@engr.sgi.com \
--cc=johnstul@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox