Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 May 2000 09:48:27 -0600
From:      Wes Peters <wes@softweyr.com>
To:        Doug Rabson <dfr@nlsystems.com>
Cc:        arch@FreeBSD.ORG
Subject:   Re: A new api for asynchronous task execution
Message-ID:  <392410CB.6B86AA@softweyr.com>
References:  <Pine.BSF.4.21.0005172131300.47945-100000@salmon.nlsystems.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Doug Rabson wrote:
> 
> The BSD/OS mutex code includes a compile-time-selected debugging feature
> which automatically detects locking hierarchy violations. Anyway, using a
> mutex here doesn't add to locking complexity since the mutex would be
> exited before calling the task's callback and re-entered after.

Wouldn't it make more sense to provide an inversion-proof semaphore?
Or is that what they're doing?

-- 
            "Where am I, and what am I doing in this handbasket?"

Wes Peters                                                         Softweyr LLC
wes@softweyr.com                                           http://softweyr.com/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?392410CB.6B86AA>