From: Michal Schmidt <mschmidt@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Jon Masters <jcm@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Subject: [PATCH] kthread: run kthreadd with max priority SCHED_FIFO
Date: Mon, 17 Dec 2007 23:43:14 +0100 [thread overview]
Message-ID: <20071217234314.540b59bd@hammerfall> (raw)
kthreadd, the creator of other kernel threads, runs as a normal
priority task. This is a potential for priority inversion when a task
wants to spawn a high-priority kernel thread. A middle priority
SCHED_FIFO task can block kthreadd's execution indefinitely and thus
prevent the timely creation of the high-priority kernel thread.
This causes a practical problem. When a runaway real-time task is
eating 100% CPU and we attempt to put the CPU offline, sometimes we
block while waiting for the creation of the highest-priority
"kstopmachine" thread.
The fix is to run kthreadd with the highest possible SCHED_FIFO
priority. Its children must still run as slightly negatively reniced
SCHED_NORMAL tasks.
Signed-off-by: Michal Schmidt <mschmidt@redhat.com>
diff --git a/kernel/kthread.c b/kernel/kthread.c
index dcfe724..a7ce932 100644
--- a/kernel/kthread.c
+++ b/kernel/kthread.c
@@ -94,10 +94,17 @@ static void create_kthread(struct kthread_create_info *create)
if (pid < 0) {
create->result = ERR_PTR(pid);
} else {
+ struct sched_param param = { .sched_priority = 0 };
wait_for_completion(&create->started);
read_lock(&tasklist_lock);
create->result = find_task_by_pid(pid);
read_unlock(&tasklist_lock);
+ /*
+ * We (kthreadd) run with SCHED_FIFO, but we don't want
+ * the kthreads we create to have it too by default.
+ */
+ sched_setscheduler(create->result, SCHED_NORMAL, ¶m);
+ set_user_nice(create->result, -5);
}
complete(&create->done);
}
@@ -217,11 +224,12 @@ EXPORT_SYMBOL(kthread_stop);
int kthreadd(void *unused)
{
struct task_struct *tsk = current;
+ struct sched_param param = { .sched_priority = MAX_RT_PRIO - 1 };
/* Setup a clean context for our children to inherit. */
set_task_comm(tsk, "kthreadd");
ignore_signals(tsk);
- set_user_nice(tsk, -5);
+ sched_setscheduler(tsk, SCHED_FIFO, ¶m);
set_cpus_allowed(tsk, CPU_MASK_ALL);
current->flags |= PF_NOFREEZE;
next reply other threads:[~2007-12-17 22:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 22:43 Michal Schmidt [this message]
2007-12-17 23:00 ` [PATCH] kthread: run kthreadd with max priority SCHED_FIFO Jon Masters
2007-12-22 9:30 ` Andrew Morton
2007-12-22 9:52 ` Jon Masters
2007-12-22 10:11 ` Andrew Morton
2007-12-22 10:18 ` Jon Masters
2007-12-22 10:39 ` Mike Galbraith
2007-12-22 10:52 ` Andrew Morton
2007-12-22 11:21 ` Jon Masters
2007-12-23 8:50 ` Mike Galbraith
2008-01-07 10:06 ` [PATCH] kthread: always create the kernel threads with normal priority Michal Schmidt
2008-01-07 10:25 ` Andrew Morton
2008-01-07 11:09 ` Ingo Molnar
2008-01-07 17:29 ` Andrew Morton
2008-01-07 17:47 ` Peter Zijlstra
2008-01-08 9:54 ` Michal Schmidt
2008-01-07 13:18 ` Michal Schmidt
2008-01-08 16:22 ` Ingo Molnar
2008-01-07 11:22 ` Remy Bohmer
2008-01-07 13:10 ` Michal Schmidt
2008-01-07 15:53 ` Remy Bohmer
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=20071217234314.540b59bd@hammerfall \
--to=mschmidt@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=jcm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=takeuchi_satoru@jp.fujitsu.com \
/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