From: Ken Keys <klkeys@west.raytheon.com>
Subject: Re: Processor Synchronization
Date: 1999/01/19
Date: 1999-01-19T00:00:00+00:00 [thread overview]
Message-ID: <36A51F3A.2207F91@west.raytheon.com> (raw)
In-Reply-To: 36A509DB.95F62C0B@pwfl.com
Marin David Condic wrote:
> The most general description of the problem domain I can come up with
is
> this: The problem is at power-up, you have to get both processors
> ticking off at the same "heartbeat" so that they have the same frame
of
> reference. Generally, you're going to have N cycles (frames, slots,
> whatever your favorite terminology is) and it is important that both
> processors be operating on cycle X at the same time. Once running,
the
> processors have to detect drift in their cycling and correct for this
so
> that they continue to both start on the same cycle at the same time.
We
> have done this sort of thing in-house, but I'm looking for a
discussion
> of a variety of algorithms and some analysis of the strengths &
> weaknesses of each.
How did you do it when did it in-house? Did you use an RTC or some other
common (hardware) time reference?
KLK
next prev parent reply other threads:[~1999-01-19 0:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-19 0:00 Processor Synchronization Marin David Condic
1999-01-19 0:00 ` Ken Keys [this message]
1999-01-20 0:00 ` Marin David Condic
1999-01-20 0:00 ` Ken Keys
1999-01-21 0:00 ` Marin David Condic
1999-01-21 0:00 ` Sune Falck
1999-01-21 0:00 ` Marin David Condic
[not found] ` <36a83fe3.3666942@news.geccs.gecm.com>
1999-01-22 0:00 ` Marin David Condic
1999-01-20 0:00 ` dennison
1999-01-21 0:00 ` The Bohemian Monk
1999-01-21 0:00 ` Marin David Condic
1999-01-22 0:00 ` Tom Ziomek
1999-01-21 0:00 ` Peter Jensen
1999-01-22 0:00 ` Al Mok
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox