From: Lee Revell <rlrevell@joe-job.com>
To: "Patrik Hägglund" <patrik.hagglund@bredband.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SCHED_RR/SCHED_FIFO and kernel threads?
Date: Thu, 16 Jun 2005 12:01:58 -0400 [thread overview]
Message-ID: <1118937719.2644.21.camel@mindpipe> (raw)
In-Reply-To: <42B199FF.5010705@bredband.net>
On Thu, 2005-06-16 at 17:25 +0200, Patrik Hägglund wrote:
> For example, in one virtual
> terminal I stared a "supervisor" shell with SCHED_FIFO at priority
> 20,
> and then the job tasks I wanted to "run" in other virtual terminals,
> now
> still with SCHED_FIFO, but with lower priorities.
I believe there's a Sysrq to drop all SCHED_FIFO processes to
SCHED_OTHER. But yes, in general, bad things will happen if you are not
careful with SCHED_FIFO.
Lee
prev parent reply other threads:[~2005-06-16 16:05 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
2005-06-22 0:13 ` Lee Revell
2005-06-16 16:01 ` Lee Revell [this message]
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=1118937719.2644.21.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patrik.hagglund@bredband.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.