Re: CLI producer code cycle starvation
Re: CLI producer code cycle starvation
- Subject: Re: CLI producer code cycle starvation
- From: "David A. Gatwood" <email@hidden>
- Date: Thu, 20 Jun 2002 09:38:38 -0700 (PDT)
On Thu, 20 Jun 2002, Jim Snyder wrote:
>
|every Mach task (process) has at least one thread. your
>
|program will have two threads (the IOProc runs in a real-time
>
|thread associated with the audio device, and then there's
>
|your main thread where your producer code ends up
>
|running).
>
>
There's one point here which is still unclear to me (thru
>
sheer ignorance of osx internals). You say that every Mach
>
process consists of one or more threads. I've been accustomed
>
to seeing threads spawned explicitly.
A process, by nature, isn't a unit of execution. It is a container for
threads. Threads are units of execution. So implicitly, every process
contains a thread. Admittedly, systems that don't support kernel-level
threading don't have this model, but otherwise, this is pretty much the
norm for unixen.
>
Does this implicit threading of processes mean that there's
>
no other setup code involved? You just act as though your
>
main process has been spawned as a thread for you, and
>
issue whatever thread calls you need to manipulate your
>
thread?
Yeah.
Later,
David
---------------------------------------------------------------------
David A. Gatwood email@hidden
Developer Docs Writer email@hidden
Apple Computer email@hidden
Check out my weekly web comic:
http://www.techmagazine.org
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.