> Can't you just make a prio 1 task which signals a prio 99 once say every
> second. If the priority 99 task doesn't get the signal after say 2
> seconds, it will look for a rt task running wild. At worst it will have to do
> an O(n) algorith when things have gone wrong, not when everything is
> working.
Well, that would work in sort of preventing a complete lockup, but the
watchdog wouldn't even know if the task eating lots of CPU is privileged
(OK) or unprivileged (not OK). Also, the original RLIMIT_RT_CPU feature
allowed you to really control how much CPU is available to unprivileged
users, not just prevent them from getting 100% CPU.
Jean-Marc
-
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]
