mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andi Kleen <ak@suse.de>, john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Joel Becker <Joel.Becker@oracle.com>
Subject: Re: [RFC][PATCH] linux-2.5.59_getcycles_A0
Date: Fri, 07 Feb 2003 17:57:46 -0800	[thread overview]
Message-ID: <516500000.1044669465@flay> (raw)
In-Reply-To: <20030208015235.GA25432@wotan.suse.de>

>> However this doesn't work on systems w/o a synced TSC, so by simply
> 
> Why not? This shouldn't be performance critical and you can make 
> it monotonous with an additional variable + lock if backwards jumps
> should be a problem.
> 
> Also the variations between non synced TSCs should be far below 
> any watchdog's radar screen.

Not true. They'll drift further and further apart over time.
Even a 0.01% crystal difference will eventually kill you.

And if that isn't bad enough think about what happens when I run 180 MHz
processors in one node, and 900MHz in another.

You really can't make any assumptions about TSC sync on boxes where
they're not synced.

M.


  reply	other threads:[~2003-02-08  1:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1044649542.18673.20.camel@w-jstultz2.beaverton.ibm.com.suse.lists.linux.kernel>
2003-02-07 21:19 ` Andi Kleen
2003-02-07 23:09   ` john stultz
2003-02-08  0:18     ` Andi Kleen
2003-02-08  0:50       ` john stultz
2003-02-08  1:52         ` Andi Kleen
2003-02-08  1:57           ` Martin J. Bligh [this message]
2003-02-08  2:14           ` john stultz
2003-02-08  2:29             ` Andi Kleen
2003-02-08  2:42               ` john stultz
2003-02-08  3:41                 ` Andi Kleen
2003-02-10 22:06               ` Bill Davidsen
2003-02-07 20:25 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=516500000.1044669465@flay \
    --to=mbligh@aracnet.com \
    --cc=Joel.Becker@oracle.com \
    --cc=ak@suse.de \
    --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

all inboxes | Powered by JetHome®