Re: IOProc limitations
Re: IOProc limitations
- Subject: Re: IOProc limitations
- From: James McCartney <email@hidden>
- Date: Thu, 31 May 2001 19:17:20 -0500
on 5/30/01 9:24 PM, Jeff Moore at email@hidden wrote:
>
The HAL doesn't touch other thread's priorities. It's IOThreads are Mach
>
real-time threads. As such, they are the highest priority threads in the
>
system, capable of pre-empting just about everything.
I had thought that OSX kernel did priority inversion, so that any thread
holding a mutex required by a high priority thread would get bumped to the
same priority. (not by the HAL but by the kernel scheduler.)
>
As a general rule, it is a really bad idea to stall the IOThread by waiting
>
on a mutex or something like that. You'll really hose your timing if the
OK. But how do you sync your threads? If you cannot use a mutex then you
cannot implement a semaphore or a condition. It would seem that you would
only have polling to fall back on to check the ioproc's progress.
--- james mccartney email@hidden <
http://www.audiosynth.com>
SuperCollider - a real time synthesis programming language for the PowerMac.
<
ftp://www.audiosynth.com/pub/updates/SC2.2.10.sea.hqx>