thanks for sharing your experience.
On 02/18/2011 02:43 PM, Daniel Poelzleithner wrote:
I assume it's here:
> Now, what you can do if you have no trust in processes at all is, to
The dynamic cgroups solution seems good.
On Android there basically is one priviledged and trusted audio process,
audioflinger, the sound server, which performs mixing and access the hardware.
All audio clients are untrusted. I think there is a need to both assign a
careful cpu.rt_runtime_us to each client but also to limit the number of clients
which can run at the same time. This would allow to keep the CPU time assigned
to all clients within a certain quota, but also to prevent clients from fighting
with each other for realtime bandwidth.
Can you limit the maximum number of realtime processes with ulatencyd?
Linux-audio-dev mailing list