* Peter Williams <[EMAIL PROTECTED]> wrote: > Oops, after rereading the patch, a task that set its RT_CPU_RATIO > rlimit to zero wouldn't be escaping the mechanism at all. It would be > suffering maximum throttling. [...]
my intention was to let 'limit 0' mean 'old RT semantics' - i.e. 'no RT CPU time for unprivileged tasks at all', and only privileged tasks may do it and then they'll get full CPU time with no throttling. so in that context your observation highlights another bug, which i fixed in the -D7 patch available from the usual place: http://redhat.com/~mingo/rt-limit-patches/ not doing the '0' exception would make it harder to introduce the rlimit in a compatible fashion. (My current thinking is that the default RT_CPU rlimit should be 0.) Ingo - 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/
