• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Limit to registered IO procs ?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Limit to registered IO procs ?


  • Subject: Re: Limit to registered IO procs ?
  • From: Andy <email@hidden>
  • Date: Fri, 21 Feb 2003 23:38:52 +0000

Begin forwarded message:

> From: Andy <email@hidden>
> Date: Fri Feb 21, 2003 23:37:44 Europe/London
> To: Jeff Moore <email@hidden>
> Subject: Re: Limit to registered IO procs ?
>
>
>
>
>
>
> On Friday, Feb 21, 2003, at 19:45 Europe/London, Jeff Moore wrote:
>> The only limits are memory.
>> But, why do you want to add so many IOProcs at once? This is
>> expensive as the HAL has to allocate resources for things that aren't
>> going to be in use.
>
>> It is much more efficient to register a single IOProc and to dispatch
>> to your specialized IOProcs from there.
>
> Thanks for the info.
>
> I would question "more efficient" ? In terms of speed surely not ?
> Admittedly the gain is small, but it is a gain, and I'm trying to
> squeeze the last ounces out our slow (ish) machines .. ;-) (pushing
> as many as 20+ channels of audio around , I need as many cycles as I
> can get).
>
> I'll change the method so that only the proc that is currently
> required is actually registered at any one time, The decision isn't
> required at runtime, I think that would be better than dispatching to
> external functions. After all why go to the bother of optimising only
> to add the overhead of an unnecessary function dispatcher. I hope
> AudioDeviceReleaseIOProc does actually release those expensive
> resources ?
>
> Perhaps at some time the documentation could mention that IOProc
> registration is expensive. I did presume it existed to do just the job
> that I was using it for. That is: one could create a set of IOProcs
> that could be dispatched from AudioDeviceStart /before/ the
> expensive decision needs to be done in the IOProc.
>
> Are there any other issues regarding resource allocation in the HAL ?
> It would be interesting to know where are the high risk areas and what
> the affects are.
_______________________________________________
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.

  • Prev by Date: Re: [ot] OS 9 boot on modern powerbooks?
  • Next by Date: ANN: RMS Buddy AU, public example code, props to CA team
  • Previous by thread: Re: Limit to registered IO procs ?
  • Next by thread: OS X 10.2.4: System Preferences crashes when USB Audio device is unplugged
  • Index(es):
    • Date
    • Thread