Re: OTMP with an Async Notifier Model
Re: OTMP with an Async Notifier Model
- Subject: Re: OTMP with an Async Notifier Model
- From: Bob Cook <email@hidden>
- Date: Mon, 9 Feb 2004 19:52:15 -0800
Hi,
Not that I'm aware of. There should be, it can be beneficial.
One item of interest in your debugging is to be aware that OS X runs
your notifier in a separate thread that can overlap execution with your
application's thread. I suspect that although ::Enqueue() is "interrupt
safe" in Carbon, its not thread safe, which is the source of the
PowerPlant woes. A few strategic additions of
::MPEnter[Exit]CriticalRegion() around the data structures shared
between the notifier and the PowerPlant application worked for my
buddy. Far from an elegant solution, but it worked.
Good luck,
Bob Cook
On 9-Feb-04, at 9:17 AM, Francois Cournoyer wrote:
Do you know if there's any ways to force the use of a single processor
instead of 2 for an application?
as our code works fine on single processors. Thought I doubt there's
really a way to do it.
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.