From: Pavel Machek <pavel@ucw.cz>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: Alex Williamson <alex.williamson@hp.com>,
george@mvista.com, john stultz <johnstul@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: Need better is_better_time_interpolator() algorithm
Date: Sat, 27 Aug 2005 13:55:32 +0200 [thread overview]
Message-ID: <20050827115531.GA1109@openzaurus.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.62.0508261231440.16138@schroedinger.engr.sgi.com>
Hi!
> > Would we ever want to favor a frequency shifting timer over anything
> > else in the system? If it was noticeable perhaps we'd just need a
> > callback to re-evaluate the frequency and rescan for the best timer. If
> > it happens without notice, a flag that statically assigns it the lowest
> > priority will due. Or maybe if the driver factored the frequency
> > shifting into the drift it would make the timer undesirable without
> > resorting to flags. Thanks,
>
> Timers are usually constant. AFAIK Frequency shifts only occur through
> power management. In that case we usually have some notifiers running
Usually is the key word here. Older APM stuff changes frequency behind
your back, and sometimes frequency shift is time-critical.
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2005-08-27 19:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 16:44 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
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 [this message]
2005-08-29 17:00 ` Christoph Lameter
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=20050827115531.GA1109@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--cc=alex.williamson@hp.com \
--cc=clameter@engr.sgi.com \
--cc=george@mvista.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
Powered by JetHome