Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] different PA2.0 CPUs in the same box?
Date: Tue, 19 Oct 1999 09:04:41 -0700	[thread overview]
Message-ID: <199910191604.JAA27382@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Mon, 18 Oct 1999 22:31:15 PDT." <199910190531.WAA27190@milano.cup.hp.com>

Grant Grundler wrote:
> Alex deVries wrote:
> > 
> > Can you mix and match different PA2.0 CPUs in a multiprocessor box?
> > An 8000 and an 8200?  
> 
> And HP hasn't mix/matched processor clock frequency's in one box either.
> 870 (4-way/PA1.0/CIO) I think had something funny about the clocks which
> I think was repeated in the T-class and possible planned in newer
> architectures. Can anyone shed more light on this?

I think I remember the problem now.

The processors can run from a "system clock" and they all run synchronous.
No chance of "clock drift" since they run at exactly the same pace.
But on systems like 870, T-class and N-class, the processors are fed clock
signals from (similar but) different sources.  Each frequency domain will
slowly drift from the "average" and thus the processor clocks need to be
resyncronized regularly.

> Minimizing clock drift of the various processors in an SMP box is
> a difficult problem. Keeping accurate time is important but
> synchronization of processors too often can really hurt performance.

grant

  reply	other threads:[~1999-10-19 16:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-18 23:03 [parisc-linux] different PA2.0 CPUs in the same box? Alex deVries
1999-10-18 23:10 ` Jim Hull
1999-10-19  5:31 ` Grant Grundler
1999-10-19 16:04   ` Grant Grundler [this message]
1999-10-19 16:55     ` Kirk Bresniker
1999-10-20 18:57       ` Grant Grundler
1999-10-19 15:40 ` R Scott Holbrook

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=199910191604.JAA27382@milano.cup.hp.com \
    --to=grundler@cup.hp.com \
    --cc=parisc-linux@thepuffingroup.com \
    /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