Subject: Re: can I bring Linux down by running "renice -20
	cpu_intensive_process"?
From: Lee Revell <rlrevell@joe-job.com>
To: Luke-Jr <luke@dashjr.org>
Cc: =?ISO-8859-1?Q?M=E5ns_Rullg=E5rd?= <mru@inprovide.com>,
       linux-kernel@vger.kernel.org
In-Reply-To: <200603120141.08129.luke@dashjr.org>
References: <441180DD.3020206@wpkg.org>
	 <Pine.LNX.4.61.0603101540310.23690@yvahk01.tjqt.qr>
	 <yw1xbqwe2c2x.fsf@agrajag.inprovide.com>
	 <200603120141.08129.luke@dashjr.org>
Content-Type: text/plain; charset=ISO-8859-1
Date: Sat, 11 Mar 2006 22:50:38 -0500
Message-Id: <1142135438.25358.55.camel@mindpipe>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 751
Lines: 18

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?

Sorry I was thinking of the -rt kernel in my previous post - in mainline
this would be effective.  In the -rt kernel you are screwed if the
spinning RT task is higher priority than the keyboard IRQ thread.

Lee

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/