From: J Sloan <jjs@toyota.com>
To: Roger Larsson <roger.larsson@skelleftea.mail.telia.com>
Cc: Christopher Friesen <cfriesen@nortelnetworks.com>,
Fred <fred@arkansaswebs.com>,
linux-kernel@vger.kernel.org
Subject: Re: Should I use Linux to develop driver for specialized ISA card?
Date: Tue, 04 Sep 2001 11:54:17 -0700 [thread overview]
Message-ID: <3B952359.84FFC7C7@lexus.com> (raw)
In-Reply-To: <E15eHup-0003ir-00@the-village.bc.nu> <01090410264000.14864@bits.linuxball> <3B950034.17909E5D@nortelnetworks.com> <200109041823.f84INqE13918@maild.telia.com>
Roger Larsson wrote:
> 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...)
Just a data point here -
The Andrew Morton patches have worked well for
me here - I test it often with quake 3 arena, and am
currently on 2.4.10-pre4 -
I was never successful in getting the kernel to
compile and run with any of the the other low
latency patches floating around -
cu
jjs
next prev parent reply other threads:[~2001-09-04 18:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 12:57 Should I use Linux to develop driver for specialized ISA card? 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
2001-09-04 18:54 ` J Sloan [this message]
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=3B952359.84FFC7C7@lexus.com \
--to=jjs@toyota.com \
--cc=cfriesen@nortelnetworks.com \
--cc=fred@arkansaswebs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.larsson@skelleftea.mail.telia.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 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.