linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Chubb <peter@chubb.wattle.id.au>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Robert Love <rml@tech9.net>,
	Chris Friesen <cfriesen@nortelnetworks.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: how to measure scheduler latency on powerpc?  realfeel doesn't work due to /dev/rtc issues
Date: Mon, 12 May 2003 15:04:09 +1000	[thread overview]
Message-ID: <16063.11081.433006.407544@wombat.chubb.wattle.id.au> (raw)
In-Reply-To: <493798056@toto.iv>

>>>>> "William" == William Lee Irwin, <William> writes:
William> Not at all. Just stamp at wakeup and difference when it runs.


That then doesn't include interrupt latency.  The nice thing about the
amlat tests is that the test predicts when the next interrupt should
occur, then measures the time between that prediction and the process
running in userspace.  If you just timestamp at wakeup, you miss all
the time between interrupt generation and noticing that the process is
to wake up.

--
Dr Peter Chubb  http://www.gelato.unsw.edu.au  peterc AT gelato.unsw.edu.au
You are lost in a maze of BitKeeper repositories,   all slightly different.

       reply	other threads:[~2003-05-12  4:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <493798056@toto.iv>
2003-05-12  5:04 ` Peter Chubb [this message]
2003-05-12  5:08   ` how to measure scheduler latency on powerpc? realfeel doesn't work due to /dev/rtc issues William Lee Irwin III
2003-05-13  2:08 how to measure scheduler latency on powerpc? realfeel doesn' t " Perez-Gonzalez, Inaky
  -- strict thread matches above, loose matches on Subject: below --
2003-05-13  0:20 Perez-Gonzalez, Inaky
2003-05-13  1:02 ` William Lee Irwin III
2003-05-10  0:39 Perez-Gonzalez, Inaky
2003-05-12 23:55 ` William Lee Irwin III
2003-05-08 22:12 how to measure scheduler latency on powerpc? realfeel doesn't " Chris Friesen
2003-05-09  0:13 ` William Lee Irwin III
2003-05-09  0:38   ` Davide Libenzi
2003-05-09  0:38     ` William Lee Irwin III
2003-05-09  0:56       ` Richard B. Johnson
2003-05-09  3:52         ` Chris Friesen
2003-05-09  4:13           ` Roland Dreier
2003-05-09  6:07             ` Chris Friesen
2003-05-09  4:26           ` William Lee Irwin III
2003-05-09  6:14             ` Chris Friesen
2003-05-09  6:20               ` William Lee Irwin III
2003-05-09  6:53                 ` Chris Friesen
2003-05-09  7:01                   ` William Lee Irwin III
2003-05-09 16:47                     ` Robert Love
2003-05-09 16:53                       ` William Lee Irwin III
2003-05-09 17:38                         ` Chris Friesen
2003-05-09 11:37               ` paubert
2003-05-09  8:23             ` mikpe

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=16063.11081.433006.407544@wombat.chubb.wattle.id.au \
    --to=peter@chubb.wattle.id.au \
    --cc=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    --cc=wli@holomorphy.com \
    /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;
as well as URLs for NNTP newsgroup(s).