All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@kihontech.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: 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: Tue, 23 Nov 2004 16:22:04 -0500	[thread overview]
Message-ID: <1101244924.32068.6.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0411231316300.2242@gradall.private.brainfood.com>

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.

-- 
Steven Rostedt
Senior Engineer
Kihon Technologies


  reply	other threads:[~2004-11-23 21:24 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 [this message]
2004-11-23 21:47           ` Lee Revell
2004-11-23 22:22             ` Steven Rostedt
2004-11-24  3:27             ` Ingo Molnar
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=1101244924.32068.6.camel@localhost.localdomain \
    --to=rostedt@kihontech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.