Re: coreaudio "ethernet audio" driver issues
Re: coreaudio "ethernet audio" driver issues
- Subject: Re: coreaudio "ethernet audio" driver issues
- From: Jeff Moore <email@hidden>
- Date: Thu, 28 Aug 2003 13:53:54 -0700
This is indeed your problem. The HAL's IO threads are higher priority
than a normal kernel work thread. So, when there is a significant
amount of work being done on the IO thread, those kernel threads don't
get to run.
USB Audio has a similar problem. It does all it's work on a secondary
interrupt that is queued from the USB driver's primary interrupt. So,
the USB Audio driver used to fall behind when there was a load in an IO
thread. In 10.2, we modified the USB driver to lay down all the info
the USB Audio driver needs from inside the USB driver's primary
interrupt. This allows the USB Audio driver to sniff the packets and
deal with them from when it gets called on the HAL's IO thread in the
case where the secondary interrupt has fallen behind due to load.
I would imagine that you would need to do similar things with your
ethernet stuff.
On Aug 28, 2003, at 11:51 AM, rimas wrote:
which leads me to believe that whats happening is that the thread
which is doing the computation for the synthesis (which ps -axM
reports as having prioirity 96 which i believe is the coreaudio
callback thread) is treated as having a higher priority by the
scheduler, causing the kernel thread which is running in the
networking part of the BSD kernel to be stalled until the synthesis
thread yields. does this sound right ??
--
Jeff Moore
Core Audio
Apple
_______________________________________________
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.