From: Ralf Baechle <ralf@linux-mips.org>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [RFC] synchronized CPU count registers on SMP machines
Date: Thu, 5 Jun 2003 02:12:32 +0200 [thread overview]
Message-ID: <20030605001232.GA5626@linux-mips.org> (raw)
In-Reply-To: <20030604164652.J19122@mvista.com>
On Wed, Jun 04, 2003 at 04:46:52PM -0700, Jun Sun wrote:
> Assuming SGI systems represent the past of MIPS, we are still ok
> future-wise. :)
You loose. The reasons why SGI did construct their systems that way are
still valid. It can be quite tricky to distribute the clock in large
systems - even for a moderate definition of large. And for ccNUMAs which
are going to show up on the embedded market sooner or later it's easy
for the lazy designer to use several clock sources anyway. Note our
current time code for will not work properly if clocks diverge on the
slightest bit - among other things the standards mandate time to
monotonically increase.
Ralf
next prev parent reply other threads:[~2003-06-05 0:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 22:39 [RFC] synchronized CPU count registers on SMP machines Jun Sun
2003-06-04 22:51 ` Michael Uhler
2003-06-04 22:51 ` Michael Uhler
2003-06-04 23:44 ` Jun Sun
2003-06-04 23:15 ` Ralf Baechle
2003-06-04 23:46 ` Jun Sun
2003-06-05 0:12 ` Ralf Baechle [this message]
2003-06-05 1:38 ` Jun Sun
2003-06-05 8:09 ` Dominic Sweetman
2003-06-05 8:48 ` Ralf Baechle
2003-06-05 16:53 ` Jun Sun
2003-06-05 20:06 ` Greg Lindahl
2003-06-05 10:45 ` Alan Cox
2003-06-05 8:55 ` Kevin D. Kissell
2003-06-05 8:51 ` Ralf Baechle
2003-06-05 8:55 ` Kevin D. Kissell
2003-06-05 11:08 ` Maciej W. Rozycki
2003-06-05 0:18 ` Keith Owens
[not found] <ralf@linux-mips.org>
2003-06-05 9:23 ` Tor Arntsen
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=20030605001232.GA5626@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=jsun@mvista.com \
--cc=linux-mips@linux-mips.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