Messages in this thread | | | Date | Sun, 14 Jul 2002 14:29:12 +0200 | From | Pavel Machek <> | Subject | Re: [patch] sched-2.5.24-D3, batch/idle priority scheduling, SCHED_BATCH |
| |
Hi!
> > > > And users of __KERNEL_SYSCALLS__ and kernel_thread() should not > > > > have policy == SCHED_BATCH. > > > > well, there's one security consequence here - module loading > > (request_module()), which spawns a kernel thread must not run as > > SCHED_BATCH. I think the right solution for that path is to set the > > policy to SCHED_OTHER upon entry, and restore it to the previous one > > afterwards - this way the helper thread has SCHED_OTHER priority. > > i've solved this problem by making kernel_thread() spawned threads drop > back to SCHED_NORMAL:
Does it mean that we now have working scheduler class that only schedules jobs when no other thread wants to run (as long as SCHED_BATCH task does not enter the kernel)? Pavel -- Worst form of spam? Adding advertisment signatures ala sourceforge.net. What goes next? Inserting advertisment *into* email? - 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/
| |