From: Karim Yaghmour <karim@opersys.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Scott Wood <scott@timesys.com>,
linux-kernel@vger.kernel.org,
"La Monte H.P. Yarroll" <piggy@timesys.com>,
Manas Saksena <manas.saksena@timesys.com>,
Bill Huey <bhuey@lnxw.com>, Philippe Gerum <rpm@xenomai.org>
Subject: Re: [patch] IRQ threads
Date: Wed, 28 Jul 2004 11:38:05 -0400 [thread overview]
Message-ID: <4107C85D.5070201@opersys.com> (raw)
In-Reply-To: <20040728062722.GA15283@elte.hu>
Ingo Molnar wrote:
> what do you think about making the i8259A's interrupt priorities
> configurable? (a'la rtirq patch) Does it make any sense, given how early
> we mask the source irq and ack the interrupt controller [hence giving
> all other interrupts a fair chance to arrive ASAP]?
>
> Bernhard Kuhn's rtirq patch is for IO-APIC/APICs, but i think the
> latency issues could be equally well fixed by not keeping the local APIC
> un-ACK-ed during level triggered irqs, but doing the mask & ack thing.
> This will be slightly slower but should make them both redirectable and
> more symmetric and fair.
Not sure why don't want to use something as architecture-specific as the
rtirq patch. We've been developing the Adeos nanokernel for 2 years now,
and it provides a uniform functionality regardless of the architecture
you are running it on. Adeos now runs on x86, PowerPC, ARM (mmu-less and
mmu-full), and IA64. Plus, RTAI now uses Adeos to run side-by-side with
Linux on at least the x86 and the PowerPC. If you're looking at
prioritizing interrupts, then Adeos' interrupt pipeline is certainly the
most compelling method available at this point in time.
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546
next prev parent reply other threads:[~2004-07-28 15:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-27 22:50 [patch] IRQ threads Scott Wood
2004-07-28 6:27 ` Ingo Molnar
2004-07-28 15:38 ` Karim Yaghmour [this message]
2004-07-28 16:01 ` Karim Yaghmour
2004-07-28 21:23 ` Bill Huey
2004-07-28 21:35 ` Scott Wood
2004-07-29 21:08 ` Bill Huey
2004-07-29 22:44 ` Ingo Molnar
2004-07-28 23:24 ` Scott Wood
2004-07-28 8:10 ` Ingo Molnar
2004-07-28 23:12 ` Scott Wood
2004-07-29 19:33 ` Ingo Molnar
2004-07-29 20:21 ` Scott Wood
2004-07-29 21:12 ` Alan Cox
2004-07-28 15:45 ` Karim Yaghmour
2004-07-28 18:28 ` Lee Revell
2004-07-28 19:12 ` Karim Yaghmour
2004-07-28 19:33 ` Lee Revell
2004-07-28 19:57 ` Karim Yaghmour
2004-07-28 20:35 ` Lee Revell
2004-07-28 21:15 ` Karim Yaghmour
2004-07-28 21:43 ` Lee Revell
2004-07-28 21:38 ` Karim Yaghmour
2004-07-28 20:21 ` Bill Huey
2004-07-28 20:42 ` Lee Revell
2004-07-28 20:46 ` Bill Huey
2004-07-28 21:48 ` Karim Yaghmour
2004-07-28 22:30 ` Bill Huey
2004-07-28 22:03 ` Philippe Gerum
-- strict thread matches above, loose matches on Subject: below --
2004-07-29 20:33 Albert Cahalan
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=4107C85D.5070201@opersys.com \
--to=karim@opersys.com \
--cc=bhuey@lnxw.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manas.saksena@timesys.com \
--cc=mingo@elte.hu \
--cc=piggy@timesys.com \
--cc=rpm@xenomai.org \
--cc=scott@timesys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox