On Mon, 7 Jan 2008 09:29:56 -0800 Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Mon, 7 Jan 2008 12:09:04 +0100 Ingo Molnar <[EMAIL PROTECTED]> wrote: > > > > > > > This causes a practical problem. When a runaway real-time task > > > > is eating 100% CPU and we attempt to put the CPU offline, > > > > sometimes we block while waiting for the creation of the > > > > highest-priority "kstopmachine" thread. > > > > sched-devel.git has new mechanisms against runaway RT tasks. > > There's a new RLIMIT_RTTIME rlimit - if an RT task exceeds that > > rlimit then it is sent SIGXCPU. > > Is that "total RT CPU time" or "elapsed time since last schedule()"? > > If the former, it is not useful for this problem. It's "runtime since last sleep" so it is useful. I still think the kthread patch is good to have anyway. The user can have other reasons to change kthreadd's priority/cpumask. Michal -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/