mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Remy Bohmer" <l.pinguin@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: [BUG+PATCH] RT-Preempt: IRQ threads running at prio 0 SCHED_OTHER
Date: Tue, 19 Dec 2006 21:52:42 +0100	[thread overview]
Message-ID: <3efb10970612191252m33e7b88cydca7fb488251ee35@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]

Hello Ingo,

I am using your yum-distributed kernel 2.6.19.1-rt15, and
unfortunately I experienced very worse latencies.
It turned out that ALL the IRQ threads were all running at prio 0, SCHED_OTHER.

Looking at the current code in kernel/irq/manage.c, the goal was to
put them at MAX_RT_PRIO, but the call to sys_sched_setscheduler()
fails with EINVAL. I have attached a patch to set them to
(MAX_RT_PRIO-1). This works.

Further I believe that each application of the RT-kernel requires a
different configuration of these thread-priorities and I prefer to
reconfigure these prios from userland during boot. As these
threadnames contain whitespaces in its name, they make the
shell-scripts unnecessary complex that I use to reconfigure the thread
priorities.
So, I would prefer a slight modification of the names: The attached
patch also changes the names from [IRQ nn] to [IRQ-nn]. I hope that
you agree with me here. (If not, I stick to do this patch each time
myself ;-) )

Kind Regards,

Remy Böhmer

[-- Attachment #2: fix-kernel-irq-thread-prio.patch --]
[-- Type: application/octet-stream, Size: 803 bytes --]

--- linux-2.6.19.i686/kernel/irq/manage.c.orig	2006-12-18 22:59:59.000000000 +0100
+++ linux-2.6.19.i686/kernel/irq/manage.c	2006-12-19 21:22:09.000000000 +0100
@@ -692,9 +692,9 @@
 	current->flags |= PF_NOFREEZE | PF_HARDIRQ;
 
 	/*
-	 * Scale irq thread priorities from prio 50 to prio 25
+	 * Scale irq thread priorities to prio 99
 	 */
-	param.sched_priority = MAX_RT_PRIO;
+	param.sched_priority = MAX_RT_PRIO-1;
 
 	sys_sched_setscheduler(current->pid, SCHED_FIFO, &param);
 
@@ -725,7 +725,7 @@
 	if (desc->thread || !ok_to_create_irq_threads)
 		return 0;
 
-	desc->thread = kthread_create(do_irqd, desc, "IRQ %d", irq);
+	desc->thread = kthread_create(do_irqd, desc, "IRQ-%d", irq);
 	if (!desc->thread) {
 		printk(KERN_ERR "irqd: could not create IRQ thread %d!\n", irq);
 		return -ENOMEM;

             reply	other threads:[~2006-12-19 20:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19 20:52 Remy Bohmer [this message]
2006-12-19 21:24 ` Ingo Molnar
2006-12-19 21:37   ` Clark Williams

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=3efb10970612191252m33e7b88cydca7fb488251ee35@mail.gmail.com \
    --to=l.pinguin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@bohmer.net \
    --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

Powered by JetHome