From: Bill Huey (hui) <billh@gnuppy.monkey.org>
To: Bernhard Kuhn <bkuhn@metrowerks.com>
Cc: linux-kernel@vger.kernel.org,
"Bill Huey (hui)" <billh@gnuppy.monkey.org>
Subject: Re: [announcement, patch] real-time interrupts for the Linux kernel
Date: Sat, 10 Jan 2004 16:02:11 -0800 [thread overview]
Message-ID: <20040111000211.GA3056@gnuppy.monkey.org> (raw)
In-Reply-To: <3FFE078D.20400@metrowerks.com>
On Fri, Jan 09, 2004 at 02:44:45AM +0100, Bernhard Kuhn wrote:
> Hi everybody!
>
> I hope that i can steal enough of your precious time to get
> your attention for a new patch that adds hard real time support
> to the linux kernel (worst case interrupt response time below
> 5 microseconds):
>
> The proposed "real time interrupt patch" enables the linux
> kernel for hard-real-time applications such as data aquisition
> and control loops by adding priorities to interrupts and spinlocks.
>
> The following document will describe the patch in detail and how
> to install it:
>
> http://home.t-online.de/home/Bernhard_Kuhn/rtirq/20040108/README
...
Also,
http://www.linuxdevices.com/news/NS3235024671.html
It's kind of a cool patch. I'm surprised that nobody's commented on this
so far. Basically, if I understand this, this uses IO-APIC hardware
assistance for getting some notion of prioritized interrupts and a other
goodies. Just ran into the article now, but the original email post flew
under my radar. /me reads more
bill
next prev parent reply other threads:[~2004-01-11 0:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 1:44 [announcement, patch] real-time interrupts for the Linux kernel Bernhard Kuhn
2004-01-11 0:02 ` Bill Huey [this message]
2004-01-11 9:14 ` Voicu Liviu
2004-01-11 16:38 ` Bernhard Kuhn
2004-01-11 19:35 ` Voicu Liviu
2004-01-11 13:24 ` Martin Schlemmer
2004-01-11 16:48 ` Bernhard Kuhn
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=20040111000211.GA3056@gnuppy.monkey.org \
--to=billh@gnuppy.monkey.org \
--cc=bkuhn@metrowerks.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