From: Roger Larsson <roger.larsson@skelleftea.mail.telia.com>
To: "Christopher Friesen" <cfriesen@nortelnetworks.com>,
Fred <fred@arkansaswebs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Should I use Linux to develop driver for specialized ISA card?
Date: Tue, 4 Sep 2001 20:19:17 +0200 [thread overview]
Message-ID: <200109041823.f84INqE13918@maild.telia.com> (raw)
In-Reply-To: <E15eHup-0003ir-00@the-village.bc.nu> <01090410264000.14864@bits.linuxball> <3B950034.17909E5D@nortelnetworks.com>
In-Reply-To: <3B950034.17909E5D@nortelnetworks.com>
On Tuesday den 4 September 2001 18:24, Christopher Friesen wrote:
> Fred wrote:
> > I'm curious, Alan, Why? I'm a hardware developer, and I would have
> > assumed that linux would have been ideal for real time / embedded
> > projects? (routers / controllers / etc.) Is there, for instance, a reason
> > to suspect that linux would not be able to respond to interrupts at say
> > 8Khz?
> > of course I know nothing of rtlinux so I'll read.
>
> I'm involved in a project where we are using linux in an embedded
> application. We've got a gig of ram, no hard drives, no video, and the only
> I/O is serial, ethernet and fiberchannel.
>
> We have a realtime process that tries to run every 50ms. We're seeing
> actual worst-case scheduling latencies upwards of 300-400ms.
>
> So while interrupts can be handled pretty quickly, you'll want to make sure
> that your buffers are big enough that your userspace app only needs to run
> every half second or so.
>
> You may be better off with rtlinux if you need better response. (Or if
> you're on x86 hardware you could look at the low-latency patches.)
1) Why shouldn't the low-latency patches work for another architecture?
Andrew Morton might be interested to fix other architectures too.
(but most patches are not in architecture specific code)
2) Montavistas reschedulable kernel is a very interesting approach, newly
released an update by Robert Love
http://kpreempt.sourceforge.net/
http://tech9.net/rml/linux/patch-rml-2.4.10-pre2-preempt-kernel-1
(there are still some spikes, but the floor is smooth)
But note you with both approaches you want to run the latency critical process
with a higher priority, and probably with the memory locked down.
See example code (latencytest) at:
http://www.gardena.net/benno/linux/audio/
(but there is no need to run at the maximum possible priority since your
process will be alone anyway...)
/RogerL
--
Roger Larsson
Skellefteå
Sweden
next prev parent reply other threads:[~2001-09-04 18:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 12:57 Rastislav Stanik
2001-09-04 13:28 ` Richard B. Johnson
2001-09-04 13:30 ` Anton Altaparmakov
2001-09-04 13:42 ` Erik Mouw
2001-09-17 19:19 ` Rogier Wolff
2001-09-04 15:15 ` Alan Cox
2001-09-04 15:26 ` Fred
2001-09-04 15:36 ` Alan Cox
2001-09-04 15:40 ` Joel Jaeggli
2001-09-04 16:24 ` Christopher Friesen
2001-09-04 17:32 ` Mark Frazer
2001-09-04 17:53 ` Christopher Friesen
2001-09-04 18:19 ` Roger Larsson [this message]
2001-09-04 18:54 ` J Sloan
2001-09-04 19:35 ` Christopher Friesen
2001-09-04 19:58 ` Andrew Morton
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=200109041823.f84INqE13918@maild.telia.com \
--to=roger.larsson@skelleftea.mail.telia.com \
--cc=cfriesen@nortelnetworks.com \
--cc=fred@arkansaswebs.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®