On Mon, Feb 14, 2011 at 05:47:40PM +0100, Robin Gareus wrote:
and whats the point of using only 3 cores for RT threads ?
other that they arent useable for normal stuff anymore ?
these threads are SCHED_FIFO. if they get runnable, they will get a
core. if the graph topology only uses 2 cores. that third core could do
somthing useful and execute SCHED_OTHER stuff.
i only see problems on the horizon.
the cgroups patch is not in jack1. if ulatencyd starts messing with
audio threads, this would probably conflict with libcgroup.
without that patch to jack, we need a whitelist.
which still prevents things from "just-work"
the root cause is probably that rt_runtime_us is in the cpu subsystem.
autogroups seem to be a lot more sensible for the jack usecase.
maybe a cgrulesengd rule for the video player... that seems like enough
i am a bit worried that we seem to have ulatencyd and cgrulesengd
competing here. this is too much based on blacklist/whitelist stuff, and
if there isnt a single format, this is going to be a big mess.
Linux-audio-user mailing list