19 Jun
2014
19 Jun
'14
8:51 p.m.
Hi Tim,
that's an interesting point.
Next week I'll be in Pisa, Italy, for a workshop held by some of the
SCHED_DEADLINE guys. I'm not a serious dev but I do research and I'll be
glad to evaluate the benefit of SCHED_DEADLINE for audio and jack,
compared to SCHED_FIFO.
Regards
Leonardo
On 19/06/2014 20:21, linux-audio-dev-request(a)lists.linuxaudio.org wrote:
since recent kernels provide SCHED_DEADLINE, i'm
porting my code to make
use of it.
* is there any plan to migrate jack1 and/or jack2 to use this scheduling
policy for the jack thread(s) of the application?
* what is the recommended way to set the scheduling policy of the jack
thread with the current API? afaict, the JackThreadInitCallback is
called before JackClient::AcquireSelfRealTime in jack2. (i cannot use
jack1 due to the old bug that jack corrupts the stack while trying to
pre-fault it)
thnx,
tim
--
Dr. Leonardo Gabrielli, PhD student
A3Lab - Dept. Information Engineering
Università Politecnica delle Marche
via Brecce Bianche 12, 60131, Ancona, Italy
Skype: leonardo.gabrielli
Web: a3lab.dii.univpm.it/people/leonardo-gabrielli
<http://a3lab.dii.univpm.it/people/leonardo-gabrielli>