From: john stultz <johnstul@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] linux-2.6.3_ia64-cyclone_A2.patch
Date: Wed, 18 Feb 2004 21:52:03 +0000 [thread overview]
Message-ID: <1077141122.985.122.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <1077136393.985.111.camel@cog.beaverton.ibm.com>
On Wed, 2004-02-18 at 13:41, David Mosberger wrote:
> Out of curiosity: what's the latency behavior for Cyclone? Do all
> nodes access a single (shared) counter or is the counter replicated on
> each node and driven by a common clock? My understanding that for
> SGI's platform it's the latter.
Unfortunately there is no replicated clock on this hardware, so all
nodes access the first counter on the first node. Not great, but correct
and slow is better then fast and wrong.
thanks
-john
next prev parent reply other threads:[~2004-02-18 21:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 20:33 [PATCH] linux-2.6.3_ia64-cyclone_A2.patch john stultz
2004-02-18 21:36 ` David Mosberger
2004-02-18 21:41 ` David Mosberger
2004-02-18 21:49 ` john stultz
2004-02-18 21:52 ` john stultz [this message]
2004-02-18 22:03 ` David Mosberger
2004-02-18 22:24 ` john stultz
2004-02-18 22:35 ` David Mosberger
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=1077141122.985.122.camel@cog.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=linux-ia64@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