public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Luke-Jr <luke@dashjr.org>
Cc: "Måns Rullgård" <mru@inprovide.com>, linux-kernel@vger.kernel.org
Subject: Re: can I bring Linux down by running "renice -20 cpu_intensive_process"?
Date: Sat, 11 Mar 2006 22:46:42 -0500	[thread overview]
Message-ID: <1142135202.25358.50.camel@mindpipe> (raw)
In-Reply-To: <200603120141.08129.luke@dashjr.org>

On Sun, 2006-03-12 at 01:41 +0000, Luke-Jr wrote:
> On Friday 10 March 2006 22:01, Måns Rullgård wrote:
> > Sysrq+n changes all realtime tasks to normal priority.
> 
> Would the kernel's main loop (where I presume Sysreq is handled) get a chance 
> to run with a constantly busy realtime task?

No, other tasks will not get to run at all.  A SCHED_FIFO task that
spins forever is a fatal bug.  Making it less dangerous would require
making it less useful.

Lee


  reply	other threads:[~2006-03-12  3:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-10 13:36 can I bring Linux down by running "renice -20 cpu_intensive_process"? Tomasz Chmielewski
2006-03-10 14:44 ` Jan Engelhardt
2006-03-10 14:52   ` Tomasz Chmielewski
2006-03-10 22:01   ` Måns Rullgård
2006-03-10 22:06     ` Jeffrey Hundstad
2006-03-11 10:42       ` Måns Rullgård
2006-03-12  1:41     ` Luke-Jr
2006-03-12  3:46       ` Lee Revell [this message]
2006-03-12  3:50       ` Lee Revell
2006-03-12  3:44     ` Lee Revell
2006-03-12 12:00       ` Måns Rullgård
2006-03-16 21:15         ` Bill Davidsen
2006-03-16 22:11           ` Lee Revell
2006-03-16 22:51           ` Måns Rullgård
2006-03-17  6:05             ` Mike Galbraith
2006-03-17 22:22               ` Måns Rullgård
2006-03-18 12:38             ` Bill Davidsen

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=1142135202.25358.50.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@dashjr.org \
    --cc=mru@inprovide.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