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: 3+ 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
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 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).