From: Bill Davidsen <davidsen@tmr.com>
To: "Måns Rullgård" <mru@inprovide.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: can I bring Linux down by running "renice -20 cpu_intensive_process"?
Date: Sat, 18 Mar 2006 07:38:16 -0500 [thread overview]
Message-ID: <441BFF38.9000300@tmr.com> (raw)
In-Reply-To: <yw1xbqw69f6j.fsf@agrajag.inprovide.com>
Måns Rullgård wrote:
>Bill Davidsen <davidsen@tmr.com> writes:
>
>
>
>>Måns Rullgård wrote:
>>
>>
>>>Lee Revell <rlrevell@joe-job.com> writes:
>>>
>>>
>>>
>>>>On Fri, 2006-03-10 at 22:01 +0000, Måns Rullgård wrote:
>>>>
>>>>
>>>>>Jan Engelhardt <jengelh@linux01.gwdg.de> writes:
>>>>>
>>>>>
>>>>>
>>>>>>>Subject: can I bring Linux down by running "renice -20
>>>>>>>cpu_intensive_process"?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>Depends on what the cpu_intensive_process does. If it tries to
>>>>>>allocate lots of memory, maybe. If it's _just_ CPU (as in `perl
>>>>>>-e '1 while 1'`), you get a chance that you can input some
>>>>>>commands on a terminal to kill it. SCHED_FIFO'ing or
>>>>>>SCHED_RR'ing such a process is sudden death of course.
>>>>>>
>>>>>>
>>>>>Sysrq+n changes all realtime tasks to normal priority.
>>>>>
>>>>>
>>>>>
>>>>A nice -20 SCHED_OTHER task is not realtime, only SCHED_FIFO and
>>>>SCHED_RR.
>>>>
>>>>
>>>Maybe extending sysrq+n to lower the priority of -20 tasks would be a
>>>good idea.
>>>
>>>
>>>
>>If it runs before the keyboard thread it doesn't matter...
>>
>>
>
>Of course not, but that's not generally the case.
>
>
>
>>But why should this hang anything, when there should be enough i/o
>>to get out of the user process. There's a good fix for this, don't
>>give this guy root any more ;-)
>>
>>
>
>Ever heard of bugs? Anyone developing a program can make a mistake.
>If the program runs with realtime scheduling a bug that makes it enter
>an infinite loop (or do something else that hogs the CPU) can be
>difficult to find since it rather efficiently locks you out.
>
>
>
Please google "emoticons" and find out what those funny characters at
the end of the of the paragraph you quoted really mean. Sheesh!
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
prev parent reply other threads:[~2006-03-18 12:36 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
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 [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=441BFF38.9000300@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.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 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.