From: Robert Love <rml@tech9.net>
To: Andrew Morton <akpm@zip.com.au>
Cc: Mike Kravetz <kravetz@us.ibm.com>, Andi Kleen <ak@muc.de>,
linux-kernel@vger.kernel.org, icollinson@imerge.co.uk,
andrea@suse.de
Subject: Re: realtime scheduling problems with 2.4 linux kernel >= 2.4.10
Date: 03 Jun 2002 13:13:27 -0700 [thread overview]
Message-ID: <1023135208.963.365.camel@sinai> (raw)
In-Reply-To: <3CFBCCB1.A8F7D16B@zip.com.au>
On Mon, 2002-06-03 at 13:08, Andrew Morton wrote:
> keventd is a "process context bottom half handler". It's designed
> for use by interrupt handlers for handing off awkward, occasional
> things which need process context. For example, device hotplugging,
> which was the original reason for its introduction.
>
> So it makes sense to give keventd SCHED_RR policy and maximum
> priority. Which should fix this problem as well, yes?
Next to ditching keventd, this is probably the best thing we can do.
I wonder how much code _really_ needs it - that is, what really needs to
be running in process-context? Obviously device hotplug probably does.
But for things like that, what about spawning (temporarily) a kernel
thread?
Robert Love
next prev parent reply other threads:[~2002-06-03 20:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 17:54 realtime scheduling problems with 2.4 linux kernel >= 2.4.10 Ian Collinson
2002-05-31 18:28 ` Mike Kravetz
2002-05-31 19:41 ` Andrea Arcangeli
2002-06-01 17:05 ` Andi Kleen
2002-06-03 16:03 ` Mike Kravetz
2002-06-03 20:08 ` Andrew Morton
2002-06-03 20:13 ` Robert Love [this message]
2002-06-03 21:09 ` Andrew Morton
2002-06-03 21:07 ` Andrea Arcangeli
2002-06-03 20:12 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2002-06-05 11:53 Ian Collinson
2002-06-05 12:17 ` Andi Kleen
2002-06-05 18:05 ` george anzinger
2002-06-05 18:13 ` Robert Love
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=1023135208.963.365.camel@sinai \
--to=rml@tech9.net \
--cc=ak@muc.de \
--cc=akpm@zip.com.au \
--cc=andrea@suse.de \
--cc=icollinson@imerge.co.uk \
--cc=kravetz@us.ibm.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