From: Jim Houston <jim.houston@attbi.com>
To: Jamie Lokier <lk@tantalophile.demon.co.uk>
Cc: linux-kernel@vger.kernel.org,
high-res-timers-discourse@lists.sourceforge.net,
jim.houston@ccur.com
Subject: Re: [PATCH] improved boot time TSC synchronization
Date: Thu, 16 Jan 2003 19:34:57 -0500 [thread overview]
Message-ID: <3E274FB1.EF85F6E0@attbi.com> (raw)
In-Reply-To: 20030116213332.GA14040@bjl1.asuk.net
Jamie Lokier wrote:
>
> It looks like not only can you synchronise with a certain accuracy,
> you can determine an upper bound on that accuracy (assuming the
> underlying CPU clocks are locked).
>
> Maybe that figure could be put into /proc/cpuinfo?
>
> As well as being an interesting value, it may be useful for programs
> to know the effective accuracy of `rdtsc'.
>
> -- Jamie
Hi Jamie,
Yeah, I'd be glad to add the round-trip time to cpuinfo. I see
this as a bogomips like metric. It tells you how quickly you
can move cache lines from chip to chip.
The patch currently prints the round-trip time and the max_delta.
On a Quad P4 Xeon, I got round-trip times in the 0.7 microsecond
range which is disappointing. The max_delta was almost always
zero cycles meaning that the feedback loop thinks that the TSC values
are perfectly synchronized.
Jim Houston - Concurrent Computer Corp.
next prev parent reply other threads:[~2003-01-17 0:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 16:44 [PATCH] improved boot time TSC synchronization Jim Houston
2003-01-16 17:54 ` David Mosberger
2003-01-16 21:33 ` Jamie Lokier
2003-01-17 0:34 ` Jim Houston [this message]
2003-01-17 1:00 ` Jamie Lokier
2003-01-17 3:35 ` Jim Houston
-- strict thread matches above, loose matches on Subject: below --
2003-01-21 1:21 Jim Houston
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=3E274FB1.EF85F6E0@attbi.com \
--to=jim.houston@attbi.com \
--cc=high-res-timers-discourse@lists.sourceforge.net \
--cc=jim.houston@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@tantalophile.demon.co.uk \
/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