Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: IOFIES Filter wakeup (was: why no IOSimpleLockSleep()?)

You can still use the interrupt disable code and a mutex lock, IOSimpleLockLock... is pretty heavy weight and you are much better off using the mutex based locks rather than the simple locks, also the interrupt disable is much better for the system as a whole.

Godfrey

On 05/20/2005, at 18:45 , Andrew Gallatin wrote:


Godfrey van der Linden writes:

The good news is that assert_wait/thread_block are a formal part of
the Mach kpi set so they are expected to work consistently and
without RRBC issues going forward.


Excellent.  And I assume that assert_wait_timeout() is included in
that formal KPI?


I think in this case you may be better off rolling your own.  I
suggest however that you don't use the
IOSimpleLockLockWithDisableInterrupt but rather iofies->disable()


Actually, I'm going to have to use a lock because wakeups can also
(rarely) come from a thread context.  But you had no way to know
that...

Thanks for the info!

Drew


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-drivers mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-drivers/email@hidden

This email sent to email@hidden
References: 
 >why no IOSimpleLockSleep()? (From: Andrew Gallatin <email@hidden>)
 >IOFIES Filter wakeup (was: why no IOSimpleLockSleep()?) (From: Godfrey van der Linden <email@hidden>)
 >Re: IOFIES Filter wakeup (was: why no IOSimpleLockSleep()?) (From: Andrew Gallatin <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.