From: Dan Malek <dan@embeddededge.com>
To: jon@eccincorp.com
Cc: Embedded Linux Forum <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Interrupt Latency
Date: Wed, 12 Jun 2002 15:25:41 -0400 [thread overview]
Message-ID: <3D07A035.4090809@embeddededge.com> (raw)
In-Reply-To: 3D0797F8.4030100@eccincorp.com
Jon Baker wrote:
> ..... It would be nice if we could
> get the
> max under 50 us. Or do you have to go to a real-time kernel?
Real-time != Real fast.......
Real-time indicates a predictable maximum/minimum, whatever is
appropriate for a given resource to be managed. Since you asked
a question that implied a maximum interrupt latency requirement,
you are designing a real-time system. Linux is not a real time
kernel, you will need to use something like RTLinux to meet such
requirements.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-12 19:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-12 18:50 Interrupt Latency Jon Baker
2002-06-12 19:25 ` Dan Malek [this message]
2002-06-12 20:16 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2002-07-19 23:55 interrupt latency Mark Hapke
2002-07-20 20:19 ` Alan Cox
2002-07-22 0:40 ` Mark Hapke
2002-07-22 13:02 ` Alan Cox
2002-08-27 9:58 Wessler, Siegfried
2002-08-27 14:11 ` Stephen Samuel
2002-08-27 17:16 ` Robert Schwebel
2002-08-27 21:44 ` Stephen Samuel
2002-08-27 17:41 ` Mark Hounschell
2002-08-27 18:01 ` Richard B. Johnson
2002-08-27 19:54 ` yodaiken
2002-08-27 20:44 ` Richard B. Johnson
2002-08-27 20:56 ` yodaiken
2002-08-27 22:47 ` Rogier Wolff
2002-08-28 12:18 ` Richard B. Johnson
2002-08-28 13:41 ` yodaiken
2002-08-28 14:25 ` Jonathan Lundell
2002-08-28 13:53 ` yodaiken
2002-08-28 15:02 ` Richard B. Johnson
2002-08-28 15:19 ` yodaiken
2002-08-28 15:31 ` Alan Cox
2002-08-28 15:37 ` Richard B. Johnson
2002-08-28 16:53 ` Randy.Dunlap
2002-08-28 12:42 ` Pavel Machek
2002-08-27 18:05 ` Dag Nygren
2002-10-30 23:50 Keith Adamson
2007-07-06 14:08 Interrupt latency Jayabrata Chakrabarty
2019-07-29 17:46 interrupt latency Muni Sekhar
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=3D07A035.4090809@embeddededge.com \
--to=dan@embeddededge.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.