From: David Mosberger <davidm@napali.hpl.hp.com>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: davidm@hpl.hp.com, "David S. Miller" <davem@redhat.com>,
Andrew Morton <akpm@digeo.com>, Andi Kleen <ak@muc.de>,
john stultz <johnstul@us.ibm.com>,
linux-kernel@vger.kernel.org,
David Mosberger <davidm@napali.hpl.hp.com>
Subject: Re: time interpolation hooks
Date: Mon, 19 May 2003 11:35:33 -0700 [thread overview]
Message-ID: <16073.9205.641605.741130@napali.hpl.hp.com> (raw)
In-Reply-To: <20030519174203.A7061@devserv.devel.redhat.com>
>>>>> On Mon, 19 May 2003 17:42:03 +0000, Arjan van de Ven <arjanv@redhat.com> said:
Arjan> On Mon, May 19, 2003 at 10:34:43AM -0700, David Mosberger wrote:
>> struct time_interpolator {
>> void (*update_wall_time) (long delta_nsec);
>> void (*reset_wall_time) (long delta_nsec);
>> unsigned long frequency; /* frequency in counts/second */
>> unsigned long drift; /* drift in parts-per-million (?) */
>> };
Arjan> probably also a "get interpolated value" kind of thing ?
Yes, of course. Not a good idea to write an email in a hurry.
Arjan> other than that it seems to match what I had in mind.
Arjan> For the score we may need something creative; I'm not sure all timers
Arjan> have a defined drift, otoh parts-per-million seems to be the
Arjan> standard mechanism of reporting this.
What could you possibly do about a timer with an unknown drift?
Perhaps give preference to higher frequency, even if the drift is
unknown? In any case, I suppose we can fine-tune the policy
afterwards.
Andrew, I assume it's OK with you if I update the ia64 code to the
proposed interface and then send you an updated patch?
--david
next prev parent reply other threads:[~2003-05-19 18:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 21:23 Andrew Morton
2003-05-16 22:00 ` David Mosberger
2003-05-17 2:38 ` David S. Miller
2003-05-19 17:34 ` David Mosberger
2003-05-19 17:42 ` Arjan van de Ven
2003-05-19 18:35 ` David Mosberger [this message]
2003-05-19 18:57 ` Andrew Morton
2003-05-20 7:26 ` David Mosberger
2003-05-19 22:37 ` David S. Miller
2003-05-19 23:03 ` David Mosberger
2003-05-19 23:08 ` David S. Miller
2003-05-17 9:09 ` Arjan van de Ven
2003-05-17 16:31 ` john stultz
2003-05-17 16:37 ` john stultz
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=16073.9205.641605.741130@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=ak@muc.de \
--cc=akpm@digeo.com \
--cc=arjanv@redhat.com \
--cc=davem@redhat.com \
--cc=davidm@hpl.hp.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