From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: SA <no_spam@ntlworld.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: interrupt latency ?
Date: Mon, 10 Feb 2003 14:58:22 +0100 [thread overview]
Message-ID: <20030210135822.GA14827@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <200302071850.52781.no_spam@ntlworld.com>
On Fri, 7 February 2003 18:50:52 +0000, SA wrote:
>
> What latency should I expect for hardware interrupts under k2.4 / i386 ?
>
>
> ie how long should it take between the hardware signalling the interrupt and
> the interrupt handler being called?
Upper limit should be ~10,000 clock cycles.
Doing some tests on ppc, some rtos was able to react within 200
cycles, linux took 1000 or so. Add whatever time you handler (the c
code) takes.
Jörn
--
When you close your hand, you own nothing. When you open it up, you
own the whole world.
-- Li Mu Bai in Tiger & Dragon
next prev parent reply other threads:[~2003-02-10 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 18:50 SA
2003-02-10 13:58 ` Jörn Engel [this message]
[not found] ` <1044889126.1438.460.camel@localhost>
2003-02-10 15:43 ` Jörn Engel
2003-02-10 16:20 ` Richard B. Johnson
2003-02-10 17:08 ` Jörn Engel
2003-02-10 18:30 ` Richard B. Johnson
2003-02-11 11:59 ` Jörn Engel
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=20030210135822.GA14827@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=no_spam@ntlworld.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
all inboxes | Powered by JetHome®