Linux IA64 platform development
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Simple Stupid Performance counters
Date: Mon, 02 May 2005 16:04:50 +0000	[thread overview]
Message-ID: <Pine.LNX.4.58.0505020901540.6038@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0504291312370.15808@schroedinger.engr.sgi.com>

On Mon, 2 May 2005, David Mosberger wrote:

> >>>>> On Fri, 29 Apr 2005 13:14:33 -0700 (PDT), Christoph Lameter <clameter@engr.sgi.com> said:
>
>   Christoph> Time is measured using the cycle counter (TSC on IA32,
>   Christoph> ITC on IA64) which has a very low latency.
>
> Very low latency?  I guess that's relative, but at 36 cycles, AR.ITC
> is one of the slowest registers.  If done properly, you can normally
> hide the latency of the first read (assuming you don't have too many
> other AR/CR accesses pending), but I see that your macros don't do
> that either:

Low latency over against the RTC which I tried to use first.

> +#define PC_START(x) x=(get_cycles() << 8) + smp_processor_id()
>
> The shift & add ensure that even PC_START() will incur the full 36
> cycle latency.

Hmm. I thought about defining two variables and passing them separately
but the current implementation worked fine.

  parent reply	other threads:[~2005-05-02 16:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-29 20:14 Simple Stupid Performance counters Christoph Lameter
2005-04-30  1:02 ` Grant Grundler
2005-04-30 18:40 ` Christoph Lameter
2005-05-02 11:39 ` David Mosberger
2005-05-02 16:04 ` Christoph Lameter [this message]
2005-05-02 16:04 ` Grant Grundler
2005-05-02 16:08 ` Christoph Lameter

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=Pine.LNX.4.58.0505020901540.6038@schroedinger.engr.sgi.com \
    --to=clameter@engr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox