30 Aug
2014
30 Aug
'14
8:08 p.m.
On Friday, August 29, 2014 09:47:25 AM Fons Adriaensen wrote:
On Fri, Aug 29, 2014 at 06:33:43PM +1000, Simon Wise
wrote:
What about pinning a core (or cores) to audio processing? If the system is
truly being stressed to the point that it has become challenging for the
scheduler to keep up, wouldn't pinning make more sense?
-Reuben
Seems that 3.14 has also added a deadline-based
scheduler that is
closer to what audio needs from realtime than the extremely low
latency preemption based on priorities that the two older realtime
schedulers offer.
http://www.linuxfoundation.org/news-media/blogs/browse/2014/01/deadline-sc
heduling-314
Not really.
The new scheduler is designed to run a set of periodic tasks,
with arbitrary periods and having few or no dependencies between
them, at up to 100% CPU usage, while meeting their deadlines.
Rate-proportional scheduling (shorter period -> higher priority)
can only do this up to 69% CPU use, except in some special cases
such as all periods being equal or having simple integer ratios
between them.