Date: Thu, 18 May 2000 09:57:19 -0600 From: Chuck Paterson <cp@bsdi.com> To: Wes Peters <wes@softweyr.com> Cc: Doug Rabson <dfr@nlsystems.com>, arch@freebsd.org Subject: Re: A new api for asynchronous task execution Message-ID: <200005181557.JAA05148@berserker.bsdi.com>
next in thread | raw e-mail | index | archive | help
} }Wouldn't it make more sense to provide an inversion-proof semaphore? }Or is that what they're doing? Not quite sure what you mean. The lock checking done now is to detect without actually having to have the deadlock occur the following thread 1 acquires lock "a" and then tries to acquire lock "b" thread 2 acquires lock "b" and then tries to acquire lock "a" There isn't really any automagic fix for this. If you are talking about running processes in order based on scheduling priority, this is propagated though mutexs which have been blocked on. Chuck 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?200005181557.JAA05148>