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>
19 Jun
19 Jun
9:17 p.m.
hi leonardo,
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.
that would be nice! the interface is much more robust than SCHED_FIFO
and it is rather similar to time-constraint threads as found on mach
threads. and it perfectly maps to rate-monotonic schedulers as found in
audio systems ...
however my initial tests were not very promising: my multicore audio
engine performed worse when using SCHED_DEADLINE for the helper threads
compared to SCHED_FIFO ...
cheers,
tim
> 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)
11:40 p.m.
On Thu, Jun 19, 2014 at 08:51:37PM +0200, Leonardo Gabrielli wrote:
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.
I'll probably be there as well. Will report on this list.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
3838
days inactive
3838
days old
linux-audio-dev@lists.linuxaudio.org
2 comments
3 participants
participants (3)
-
Fons Adriaensen -
Leonardo Gabrielli -
tim