[music-dsp] implementing sequencer...

[Chris Parsons]

True, but some of us like to live dangerously :)

I would only ever use REALTIME thread priority on a thread that has
predicable behaviour and isn't dependent on anything else.  It is dangerous
because if the thread locks so does your system most of the time.  REALTIME
priority level is probably bad for any kind of I/O thread for that matter.

I use it very occasionally and sparingly, and most certainly carefully.  For
most high priority systems as you say, THREAD_PRIORITY_HIGHEST along with
raising the process priority is more than enough.



-----Original Message-----
From: xk [mailto:xk at myrealbox.com]
Sent: jeudi 18 avril 2002 17:34
To: music-dsp at shoko.calarts.edu
Subject: Re: [music-dsp] implementing sequencer...


> thread priority REALTIME you've got a very good chance of getting the CPU
> back at the end of your sleep.

Realtime priority should never be used. It's dangerous, as the kernel cannot
control anymore that process. If the process won't release the CPU
frequently, the system will behave strangly, the disk buffers won't be
flushed anymore, ...

HIGH_PRIORITY_CLASS together with THREAD_PRIORITY_HIGHEST for the audio
thread is more than enough.

dupswapdrop -- the music-dsp mailing list and website: subscription info,
FAQ, source code archive, list archive, book reviews, dsp links
http://shoko.calarts.edu/musicdsp/