| |||||||||||||
Audio latency goes full circleAudio latency goes full circlePosted Feb 18, 2005 1:56 UTC (Fri) by andyh (guest, #26163)Parent article: Audio latency goes full circle
I don't understand why universal access to limited real time features would be harmfull on a desktop system. If most systems allowed real-time processes to consume at most 20% of the cpu, trying to get more cpu time by using real time mode would result in the program getting less cpu time. 20% should be enough to run normal applications like an audio player, a hardware accelerated pvr application, or a basic sound recorder.
I don't understand how the possibility that an application could hog 20% of the cpu could be a security violation on a desktop machine. If a normal user dislikes a Free or proprietary application hogging their cpu, they don't edit the source and recompile it -- they uninstall it.
(Log in to post comments)
Audio latency goes full circle Posted Feb 18, 2005 6:15 UTC (Fri) by conman (guest, #14830) [Link] Because a fully cpu bound application locks up the whole machine, which it does not do with normal cpu scheduling policies. Running the application "yes" with real time scheduling will lock up the machine.
Audio latency goes full circle Posted Feb 19, 2005 18:48 UTC (Sat) by andyh (guest, #26163) [Link] I believe that the proposed patches would throttle back any process that exceeded a user set cpu limit.
|
|||||||||||||