On 10/29/07, <b class="gmail_sendername">Lee Revell</b> <<a href="mailto:rlrevell@joe-job.com">rlrevell@joe-job.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 10/29/07, Chuckk Hubbard <<a href="mailto:badmuthahubbard@gmail.com">badmuthahubbard@gmail.com</a>> wrote:<br>> Update: I just discovered that running jackd -R -P 70 -dalsa -P -p256 -n2<br>> -r44100 as ROOT doesn't even set priority 70. jackd then runs as a root
<br>> process with priority 20, according to both chrt and top.<br>> Apparently my system is not able to run anything higher than 20 priority;<br>> does this mean my kernel is misconfigured, or might it be something else?
<br><br>jackd is a multithreaded process, you can't just look at the priority<br>of the main thread, you have to check all of them. It should have<br>some SCHED_FIFO threads and some SCHED_NORMAL threads.</blockquote>
<div><br>Interesting, I'll have to keep reading until I find out how to do that.<br>But is it normal, then, that chrt -p 70 `pidof "jackd"` would set rtprio 70 but jackd -R -P 70 etc. wouldn't?<br>Which is to say, if chrt can set the main thread priority, why not the -P flag?
<br><br>-Chuckk<br><br></div></div><br>-- <br><a href="http://www.badmuthahubbard.com">http://www.badmuthahubbard.com</a>