Lennart, I am still trying to understand what the basic rationale is
here. 3 years ago, the kernel mailing discussed RT scheduling and
decided that RLIMIT_RTPRIO was the way to handle access to this
capability. That decision was made knowing that some user-space
infrastructure would be necessary to make it usable for most
end-users. So, 3 years on, that user space infrastructure hasn't been
created, and now your proposed solution is to provide a different
method of accessing RT scheduling. Are you arguing/suggesting that the
user-space infrastructure will never be created because of the
security issues? Are you suggesting that the original decision to
focus on RLIMIT_RTPRIO was a mistake that didn't take "the reality of
what mainstream distros will do" into account?
--p
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Received on Mon Jun 22 20:15:02 2009
This archive was generated by hypermail 2.1.8 : Mon Jun 22 2009 - 20:15:02 EEST