IEEE80211_LOCK/WI_LOCK concerns in 802.11 framework

Jason Thorpe points out today that the semantics of splnet are a
lot different from the locking primitive in FreeBSD. Consequently,
certain locking patterns that are safe with NetBSD's implementation of
IEEE80211_LOCK/WI_LOCK will deadlock FreeBSD.

I guess that FreeBSD uses the new locking mechanism for efficiency on
multiprocessor systems?

Maybe the set of locking macros in common needs to be enriched, with
four or more macros instead of two?  For example, maybe a pair that
block/unblock interrupts, and another pair that synchronize access to
data structures (a no-op in NetBSD, a mutex lock in Free)?

Thoughts?

Dave

-- 
David Young             OJC Technologies
[email protected]      Urbana, IL * (217) 278-3933
--
*bsd wireless list, a bawug thing <http://www.bawug.org/>
[un]subscribe: http://lists.bawug.org/mailman/listinfo/bsd-wireless/