Next: Semaphores, Previous: Atomic Operations, Up: Threading
Mutexes are used for controlling access to a shared resource. One thread is allowed to hold the mutex, others which attempt to take it will be made to wait until it's free. Threads are woken in the order that they go to sleep.
There isn't a timeout on mutex acquisition, but the usual WITH-TIMEOUT macro (which throws a TIMEOUT condition after n seconds) can be used if you want a bounded wait.
(defpackage :demo (:use "CL" "SB-THREAD" "SB-EXT")) (in-package :demo) (defvar *a-mutex* (make-mutex :name "my lock")) (defun thread-fn () (format t "Thread ~A running ~%" *current-thread*) (with-mutex (*a-mutex*) (format t "Thread ~A got the lock~%" *current-thread*) (sleep (random 5))) (format t "Thread ~A dropped lock, dying now~%" *current-thread*)) (make-thread #'thread-fn) (make-thread #'thread-fn)
Current owner of the mutex,
nil
if the mutex is free. May return a stale value, usemutex-owner
instead.
Deprecated in favor of
grab-mutex
.
Release
mutex
by setting it tonil
. Wake up threads waiting for this mutex.
release-mutex
is not interrupt safe: interrupts should be disabled around calls to it.If the current thread is not the owner of the mutex then it silently returns without doing anything (if
if-not-owner
is :PUNT), signals awarning
(ifif-not-owner
is :WARN), or releases the mutex anyway (ifif-not-owner
is :FORCE).
Acquire
mutex
for the dynamic scope ofbody
, setting it tovalue
or some suitable default value ifnil
. Ifwait-p
is non-NIL and the mutex is in use, sleep until it is available
Acquires
mutex
for the dynamic scope ofbody
. Within that scope further recursive lock attempts for the same mutex succeed. It is allowed to mixwith-mutex
andwith-recursive-lock
for the same mutex provided the default value is used for the mutex.