All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rich Altmaier <richa@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] - sched_clock() broken for ia64 SN platform
Date: Thu, 20 Nov 2003 17:25:59 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106934978121449@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106928980122896@msgid-missing>

Just to add a small note to Jack's comments, the reason for the
existance of this "globally synchronized hi-res" counter is exactly
for scheduling.  On IRIX we use this in the frame-scheduler, to
achieve order(tens of microsecond) simultaneous launch of processes on
multiple CPUs for hard realtime.

The counter is replicated in each memory controller, where the
NUMAflex interconnect provides a broadcast clock signal to drive them.
It's a fairly cool feature, and the realtime people love it...

FYI, Rich


Jack Steiner wrote:

> 
> 
> This is slightly off-topic, but the shared platform counter on the SGI 
> platform isnt a single counter. The counter is replicated in each chipset
> It is synchronized thruout the system so that all cpus will see
> the same value - ie., no drift. Reading the counter does not required any 
> off-node references. There shouldnt be any scaling issues. However,
> reading the ITC is faster & preferred if intercpu drift is not an issue.
> 
> 



  parent reply	other threads:[~2003-11-20 17:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20  0:56 [PATCH] - sched_clock() broken for ia64 SN platform John Hawkes
2003-11-20  1:24 ` David Mosberger
2003-11-20  4:09 ` John Hawkes
2003-11-20  6:01 ` David Mosberger
2003-11-20 15:23 ` Jack Steiner
2003-11-20 17:25 ` Grant Grundler
2003-11-20 17:25 ` Rich Altmaier [this message]
2003-11-20 18:32 ` David Mosberger
2003-11-20 19:20 ` Robin Holt
2003-11-20 19:23 ` Robin Holt
2003-11-20 20:58 ` John Hawkes
2003-11-20 21:27 ` David Mosberger
2003-11-20 21:58 ` john stultz
2003-11-20 22:14 ` John Hawkes

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=marc-linux-ia64-106934978121449@msgid-missing \
    --to=richa@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.