public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: john stultz <johnstul@us.ibm.com>,
	Chris Friesen <cfriesen@nortelnetworks.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: high res timestamps and SMP
Date: Fri, 21 Nov 2003 06:46:44 +1100	[thread overview]
Message-ID: <20031120194644.GA11889@krispykreme> (raw)
In-Reply-To: <16316.38292.729957.491201@alkaid.it.uu.se>


Hi,

> Last time I checked, all 32-bit PowerPC chips ran that clock at 1/4
> of the bus clock speed.

It depends on the chip, on recent ppc64 boxes its 1/8 of the processor
clock speed.

> That may be adequate for time-of-day and I/O delays and such, but
> it's worthless for timestamps or performance measurements.

Can you show me the application that depends on timestamps being that
accurate?

Running the multiplier at a set fraction of the processor speed
is a good idea I think. Go look at any large x86 box (and possibly ia64
box) and you will find the timebases are not synced. Even our biggest
box has the timebase synced, its easy to do when the timebase is running
at a reasonable rate.

In a trade off between unsynced timebases and timebase running at a
fraction of the cpu speed, ill take the latter :) (Ask the x86 guys what
a pain unsynced timebases are)

Anton

  reply	other threads:[~2003-11-20 19:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19 22:40 high res timestamps and SMP Chris Friesen
2003-11-20  3:02 ` john stultz
2003-11-20 10:21   ` Mikael Pettersson
2003-11-20 19:46     ` Anton Blanchard [this message]
2003-11-20 22:31       ` Chris Friesen

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=20031120194644.GA11889@krispykreme \
    --to=anton@samba.org \
    --cc=cfriesen@nortelnetworks.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    /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