From: "K.R. Foley" <kr@cybsft.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: v2.6.20-rt1, yum/rpm
Date: Wed, 28 Feb 2007 04:16:04 -0600 [thread overview]
Message-ID: <45E55664.90407@cybsft.com> (raw)
In-Reply-To: <20070228081132.GA32405@elte.hu>
Ingo Molnar wrote:
> * K.R. Foley <kr@cybsft.com> wrote:
>
>> Ingo Molnar wrote:
>>> i have released the v2.6.20-rt1 kernel, which can be downloaded from the
>>> usual place:
>>>
>> I have a couple of questions regarding priorities of the softirqs, IRQ
>> handlers, etc.
>>
>> With some exceptions, back in 2.6.18 and prior patches the IRQ threads
>> were prioritized between 50 and 25 and the most of the softirqs were
>> prioritized at 1? In newer patches it looks like they are all
>> prioritized at 50?
>>
>> I was just curious what went into making these choices? I am just
>> trying to better understand these decisions.
>
> The basically random order-of-request_irq() prioritization was causing
> problems (it worked for some but didnt work for others), so i got rid of
> trying to auto-guess some priority order. Also, now that we've got
> tools/scripts like set_kthread_prio and rtprio it seemed more consistent
> to just not attempt to prioritize interrupts and softirqs at all, but to
> keep them all 'in the middle' of the RT priority range.
>
> Ingo
>
Thanks.
--
kr
next prev parent reply other threads:[~2007-02-28 10:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 6:56 v2.6.20-rt1, yum/rpm Ingo Molnar
2007-02-05 9:18 ` Serge Belyshev
2007-02-05 9:02 ` Ingo Molnar
2007-02-05 10:36 ` Sunil Naidu
2007-02-05 10:42 ` Peter Zijlstra
2007-02-05 10:22 ` Ingo Molnar
2007-02-05 11:15 ` Sunil Naidu
2007-02-05 12:59 ` Michal Piotrowski
2007-02-05 13:47 ` Ingo Molnar
2007-02-05 21:29 ` Michal Piotrowski
2007-02-05 14:25 ` Karsten Wiese
2007-02-05 21:50 ` Michal Piotrowski
2007-02-06 0:11 ` Michal Piotrowski
2007-02-06 1:14 ` Daniel Walker
2007-02-06 10:05 ` Pre-packaged version Alessio Igor Bogani
2007-02-06 10:10 ` v2.6.20-rt1, yum/rpm Arjan van de Ven
2007-02-07 12:32 ` Ingo Molnar
2007-02-06 10:30 ` Sunil Naidu
2007-02-06 19:38 ` Chuck Harding
2007-02-06 20:08 ` K.R. Foley
2007-02-27 17:39 ` K.R. Foley
2007-02-28 8:11 ` Ingo Molnar
2007-02-28 10:16 ` K.R. Foley [this message]
2007-04-26 13:57 ` v2.6.21-rt1 Ingo Molnar
2007-04-26 20:53 ` v2.6.21-rt1 Free Ekanayaka
2007-05-03 19:16 ` v2.6.21-rt1 - bug in asm-mips/atomic.h Tim Bird
2007-05-03 19:35 ` v2.6.21-rt1 - mips compile bugs Tim Bird
2007-05-17 18:46 ` v2.6.21-rt1 emin ak
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=45E55664.90407@cybsft.com \
--to=kr@cybsft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).