public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Patrik Hägglund" <patrik.hagglund@bredband.net>
To: linux-kernel@vger.kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Chris Friesen <cfriesen@nortel.com>
Subject: Re: SCHED_RR/SCHED_FIFO and kernel threads?
Date: Wed, 22 Jun 2005 00:18:15 +0200	[thread overview]
Message-ID: <42B89227.6050501@bredband.net> (raw)
In-Reply-To: <42B3D7E2.2070600@bredband.net>

Well, Ingo's patch didn't made any difference for my problem with kernel 
starvation.

As expected, the workaround of raising the priority of the 'events' 
kernel thread made it possible to switch VT or switch windows in X (as 
described in my first mail), when running a simple infinite loop. When 
running arbitrary programs, I expect that all kernel threads needs 
higher priority.

I guess that the point with kernel threads is to push heavy kernel 
requests "backwards in the queue", thereby lowering the mean latency for 
SHED_OTHER processes. Therefore, using high priorities for kernel 
threads was not an option. However, this comes at the price of breaking 
SCHED_FIFO/SCHED_RR.

The only clean solution is probably to have priorities that are 
exclusively reserved for use by the kernel. I saw that kernel threads in 
LynxOS may use a priority of 1/2 above of the user-space tasks it 
serves. This seems like a good solution to the problem.

Any other patches out there, ready for a test?

/Patrik Hägglund

  parent reply	other threads:[~2005-06-21 22:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16 15:25 SCHED_RR/SCHED_FIFO and kernel threads? Patrik Hägglund
2005-06-16 15:48 ` Chris Friesen
2005-06-17  6:38   ` Patrik Hägglund
2005-06-17 12:37     ` Steven Rostedt
2005-06-18  8:14       ` Patrik Hägglund
2005-06-21 22:15         ` Patrik Hägglund
2005-06-21 22:18         ` Patrik Hägglund [this message]
2005-06-22  0:13           ` Lee Revell
2005-06-16 16:01 ` Lee Revell

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=42B89227.6050501@bredband.net \
    --to=patrik.hagglund@bredband.net \
    --cc=cfriesen@nortel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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