linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: root@chaos.analogic.com
Cc: William Lee Irwin III <wli@holomorphy.com>,
	Davide Libenzi <davidel@xmailserver.org>,
	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: Thu, 08 May 2003 23:52:29 -0400	[thread overview]
Message-ID: <3EBB25FD.7060809@nortelnetworks.com> (raw)
In-Reply-To: Pine.LNX.4.53.0305082052160.21290@chaos

Richard B. Johnson wrote:
> On Thu, 8 May 2003, William Lee Irwin III wrote:
>>>>Why would you want to use an interrupt? Just count jiffies in sched.c

I'm trying to get a feel for the maximum time from an interrupt coming in until 
the userspace handler gets notified.  On intel you can program the hardware to 
generate interupts through /dev/rtc.  The powerpc doesn't seem to support this.

Jiffies are not accurate enough, I am expecting max latencies in the 1-2 ms range.

> Does it have a printer port like the Intel machines?

Unfortunately no.  USB/Firewire/Ethernet on the desktop, ethernet/serial for 
compactPCI.

I want to find an additional programmable interrupt source.  It bites that cheap 
PCs have this, and the powerpc doesn't.

Chris



-- 
Chris Friesen                    | MailStop: 043/33/F10
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com


  reply	other threads:[~2003-05-09  3:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-08 22:12 how to measure scheduler latency on powerpc? realfeel doesn't work due to /dev/rtc issues 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 [this message]
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
2003-05-09  8:17 ` how to measure scheduler latency on powerpc? realfeel doesn Giuliano Pochini
2003-05-10  0:39 how to measure scheduler latency on powerpc? realfeel doesn' t work due to /dev/rtc issues Perez-Gonzalez, Inaky
2003-05-12 23:55 ` William Lee Irwin III
     [not found] <493798056@toto.iv>
2003-05-12  5:04 ` how to measure scheduler latency on powerpc? realfeel doesn't " Peter Chubb
2003-05-12  5:08   ` William Lee Irwin III
2003-05-13  0:20 how to measure scheduler latency on powerpc? realfeel doesn' t " Perez-Gonzalez, Inaky
2003-05-13  1:02 ` William Lee Irwin III
2003-05-13  2:08 Perez-Gonzalez, Inaky

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=3EBB25FD.7060809@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    --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).