Date: Wed, 09 May 2012 11:21:50 -0400 From: Joe Marcus Clarke <marcus@marcuscom.com> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Questions on adaptive mutexes and trylock Message-ID: <4FAA8B8E.2070506@marcuscom.com>
next in thread | raw e-mail | index | archive | help
The newest GLib (as well as PHP APC) is starting to use adaptive mutexes in their code. When a mutex type is set to adaptive and you try to call pthread_mutex_trylock() on it, you get back an EINVAL. Is this a bug, or should this really be happening (the code clearly indicates adaptive mutexes are not handled by trylock)? I imagine Linux is not doing this since the code doesn't abort on Linux as it does on FreeBSD. Should we be silently allowing trylock to perform a no-op on adaptive mutexes, or should we be handling adaptive mutexes with trylock? Thanks. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FAA8B8E.2070506>