* RT priority 99 on soundcard
@ 2014-03-31 5:18 Joël Krähemann
2014-03-31 7:43 ` Clemens Ladisch
0 siblings, 1 reply; 2+ messages in thread
From: Joël Krähemann @ 2014-03-31 5:18 UTC (permalink / raw)
To: alsa-devel
Is running on top of soundcard with realtime priority 99 problematic?
/* and now async */
{
static const struct timespec req = {
0,
(250000000 * (1 / 45)),
};
if(!AGS_IS_DEVOUT_THREAD(thread)){
nanosleep(&req, NULL);
}
}
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: RT priority 99 on soundcard
2014-03-31 5:18 RT priority 99 on soundcard Joël Krähemann
@ 2014-03-31 7:43 ` Clemens Ladisch
0 siblings, 0 replies; 2+ messages in thread
From: Clemens Ladisch @ 2014-03-31 7:43 UTC (permalink / raw)
To: Joël Krähemann, alsa-devel
Joël Krähemann wrote:
> Is running on top of soundcard with realtime priority 99 problematic?
If that thread ever goes into an infinite loop, you won't be able to
stop it easily.
Please note that priorities are relative, i.e., your thread's priority
needs to be higher than that of any other thread that you want to be
able to interrupt, but less than that of a more important thread.
How to order the specific threads on your particular system is your own
decision.
Regards,
Clemens
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-03-31 7:43 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-03-31 5:18 RT priority 99 on soundcard Joël Krähemann
2014-03-31 7:43 ` Clemens Ladisch
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox