From: Ingo Molnar <mingo@elte.hu>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Steven Rostedt <rostedt@kihontech.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm2-V0.7.29-0, and 30-9
Date: Wed, 24 Nov 2004 04:27:57 +0100 [thread overview]
Message-ID: <20041124032757.GB12028@elte.hu> (raw)
In-Reply-To: <1101246438.1594.3.camel@krustophenia.net>
* Lee Revell <rlrevell@joe-job.com> wrote:
> On Tue, 2004-11-23 at 16:22 -0500, Steven Rostedt wrote:
> > Just curious to why you scale the interrupts from 49 down to 25. What
> > would be wrong with keeping all of them at 49 (or whatever). Being a
> > FIFO, no interrupt would preempt another. Why would you want the first
> > IRQs to be registered have higher priority than (and thus will preempt)
> > irqs registered later.
>
> I raised this issue before. I agree that all interrupts should get
> the same RT prio by default. Otherwise the default behavior is
> arbitrary.
i agree that it's arbitrary. There are two reasons for the ordering:
1) _usually_ the IRQs that get registered first are the 'more important'
ones. E.g. timer and keyboard interrupts will preempt the IDE
interrupt. This is in no way a generic thing though.
2) testing: if all IRQs are at the same priority level then alot less
inter-IRQ preemption occurs, and testing coverage is lower. With all
irqs on different levels the bugs will trigger sooner.
To solve this cleanly some userspace policy code is needed that would
take some settings (e.g. sound_highprio) through which the priority
setup could be configured. It's not a simple task as that could would
have to discover the type of devices that are in the system and their
irqs - possibly a component of udev could do this?
Ingo
next prev parent reply other threads:[~2004-11-24 2:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 16:06 [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm2-V0.7.30-2 Mark_H_Johnson
2004-11-22 22:12 ` Ingo Molnar
2004-11-22 21:21 ` K.R. Foley
2004-11-23 11:46 ` Ingo Molnar
2004-11-23 4:43 ` Adam Heath
2004-11-23 11:52 ` Ingo Molnar
2004-11-23 18:07 ` Adam Heath
2004-11-23 19:17 ` [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm2-V0.7.29-0, and 30-9 Adam Heath
2004-11-23 21:22 ` Steven Rostedt
2004-11-23 21:47 ` Lee Revell
2004-11-23 22:22 ` Steven Rostedt
2004-11-24 3:27 ` Ingo Molnar [this message]
2004-11-24 4:06 ` [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm2-V0.7.30-2 Ingo Molnar
2004-11-24 9:00 ` Adam Heath
2004-11-25 3:22 ` Adam Heath
2004-11-25 17:02 ` Ingo Molnar
2004-11-25 17:13 ` Adam Heath
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=20041124032757.GB12028@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=rostedt@kihontech.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
all inboxes | Powered by JetHome®