public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Mike Kravetz <kravetz@us.ibm.com>
Cc: 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: Mon, 03 Jun 2002 13:08:17 -0700	[thread overview]
Message-ID: <3CFBCCB1.A8F7D16B@zip.com.au> (raw)
In-Reply-To: <C0D45ABB3F45D5118BBC00508BC292DB09C992@imgserv04> <20020531112847.B1529@w-mikek2.des.beaverton.ibm.com> <m37kljkjys.fsf@averell.firstfloor.org> <20020603090328.A1581@w-mikek2.des.beaverton.ibm.com>

Mike Kravetz wrote:
> 
> ...
> Seems that this tells people to leave a high priority real-
> time shell running on the console.  However, if one can not
> get to the console, then there is no point in leaving a high
> priority shell running there.  Part of the problem may be
> in the definition of 'console'.  Different console implementations
> behave differently.
> 
> Is this something we should 'fix'?  I would envision a 'solution'
> for each console implementation.  OR we could remove the above
> from the man page. :)
> 

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?

keventd is also being (ab)used for performing disk I/O.
You know who you are ;)  But even given that, I don't expect
that elevating its policy&priority will cause any problems.

-

  reply	other threads:[~2002-06-03 20:09 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 [this message]
2002-06-03 20:13         ` Robert Love
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=3CFBCCB1.A8F7D16B@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=ak@muc.de \
    --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