Patrik Hägglund wrote:
Kernel threads seems to generally be scheduled in the SCHED_OTHER class
(with the 'migration' thread as an exception).
This is on purpose. The idea is that realtime processes get all the
time they request. If the kernel threads are interrupting the realtime
app, then the latency of the realtime app is degraded.
As I see it, "kernel activity" shall not be starved by user-space
processes. Therefore, I was very suprised by this behaviour when I saw
it in 2.6.11.
If you want specific kernel threads to take priority, you can always
manually make then SCHED_RR/SCHED_FIFO yourself.
Chris
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
