From: Jon Baker <jon@eccincorp.com>
To: Embedded Linux Forum <linuxppc-embedded@lists.linuxppc.org>
Subject: Interrupt Latency
Date: Wed, 12 Jun 2002 14:50:32 -0400 [thread overview]
Message-ID: <3D0797F8.4030100@eccincorp.com> (raw)
I am curious about interrupt latency.
I have an Embedded Planet RPX Classic CLLF_BW31 MPC860 running at 48Mhz with
non-realtime Hard Hat 1.2 with the 2.2.14 kernel.
In general what kind of interrupt latency can I expect? I am seeing a pretty
consistent 10 us min IRQ2 latency but occassionally see up to 70 us max. I am
not using IRQ0 or IRQ1 (therefore IRQ2 is highest priority) and we monitored
this with my application code doing next to nothing. Basically I am only
running ISR2. First, I was surprised the 10 us min latency, I thought I might
occassionally see a much quicker response. Second, I was surprised to see the
occassional slow response of 70 us max. It would be nice if we could get the
max under 50 us. Or do you have to go to a real-time kernel? I am looking into
my code to see that I am not masking the interrupt for too long (or even at all)
and checking the driver code efficiency. Could the non-realtime linux kernel
mask the interrupts for that long? I am going to look into what all linux is
doing, I am thinking it is not doing much but have not verified this. I tried
to find some general interrupt latency numbers on the web through Monta Vista or
others but did not find anything relevant.
Jon Baker
===================================
Jon Baker
Software Engineer
Efficient Channel Coding, Inc.
216-635-1610
www.eccincorp.com
===================================
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-06-12 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-12 18:50 Jon Baker [this message]
2002-06-12 19:25 ` Interrupt Latency Dan Malek
2002-06-12 20:16 ` Wolfgang Denk
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=3D0797F8.4030100@eccincorp.com \
--to=jon@eccincorp.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).