From: Andi Kleen <ak@muc.de>
To: Mike Kravetz <kravetz@us.ibm.com>
Cc: 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: 01 Jun 2002 19:05:47 +0200 [thread overview]
Message-ID: <m37kljkjys.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <C0D45ABB3F45D5118BBC00508BC292DB09C992@imgserv04> <20020531112847.B1529@w-mikek2.des.beaverton.ibm.com>
Mike Kravetz <kravetz@us.ibm.com> writes:
> This works fine for me on 2.4.17 with a SERIAL console. Could this
> be related to some differences (new features) in the VGA console?
> I am totally ignorant of how the consoles work.
One possibility is that something relies on schedule_task() - keventd
doesn't run with realtime priority and can be starved.
Seems to be the case indeed:
/usr/src/linux/drivers/char% grep schedule_task *.c
console.c: schedule_task(&console_callback_tq);
...
the console switch does.
Fixing it would require boosting keventd's priority either globally
or temporarily. E.g. if the original reporter could put this
(untested/uncompiled) at the beginning of kernel/context.c:context_thread():
current->policy = SCHED_RR;
current->rt_priority = 99;
it could fix his problem.
-Andi
next prev parent reply other threads:[~2002-06-01 17:06 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 [this message]
2002-06-03 16:03 ` Mike Kravetz
2002-06-03 20:08 ` Andrew Morton
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=m37kljkjys.fsf@averell.firstfloor.org \
--to=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