diff options
author | Georg Brandl <georg@python.org> | 2007-08-15 14:28:22 (GMT) |
---|---|---|
committer | Georg Brandl <georg@python.org> | 2007-08-15 14:28:22 (GMT) |
commit | 116aa62bf54a39697e25f21d6cf6799f7faa1349 (patch) | |
tree | 8db5729518ed4ca88e26f1e26cc8695151ca3eb3 /Doc/library/mutex.rst | |
parent | 739c01d47b9118d04e5722333f0e6b4d0c8bdd9e (diff) | |
download | cpython-116aa62bf54a39697e25f21d6cf6799f7faa1349.zip cpython-116aa62bf54a39697e25f21d6cf6799f7faa1349.tar.gz cpython-116aa62bf54a39697e25f21d6cf6799f7faa1349.tar.bz2 |
Move the 3k reST doc tree in place.
Diffstat (limited to 'Doc/library/mutex.rst')
-rw-r--r-- | Doc/library/mutex.rst | 62 |
1 files changed, 62 insertions, 0 deletions
diff --git a/Doc/library/mutex.rst b/Doc/library/mutex.rst new file mode 100644 index 0000000..523692f --- /dev/null +++ b/Doc/library/mutex.rst @@ -0,0 +1,62 @@ + +:mod:`mutex` --- Mutual exclusion support +========================================= + +.. module:: mutex + :synopsis: Lock and queue for mutual exclusion. +.. sectionauthor:: Moshe Zadka <moshez@zadka.site.co.il> + + +The :mod:`mutex` module defines a class that allows mutual-exclusion via +acquiring and releasing locks. It does not require (or imply) threading or +multi-tasking, though it could be useful for those purposes. + +The :mod:`mutex` module defines the following class: + + +.. class:: mutex() + + Create a new (unlocked) mutex. + + A mutex has two pieces of state --- a "locked" bit and a queue. When the mutex + is not locked, the queue is empty. Otherwise, the queue contains zero or more + ``(function, argument)`` pairs representing functions (or methods) waiting to + acquire the lock. When the mutex is unlocked while the queue is not empty, the + first queue entry is removed and its ``function(argument)`` pair called, + implying it now has the lock. + + Of course, no multi-threading is implied -- hence the funny interface for + :meth:`lock`, where a function is called once the lock is acquired. + + +.. _mutex-objects: + +Mutex Objects +------------- + +:class:`mutex` objects have following methods: + + +.. method:: mutex.test() + + Check whether the mutex is locked. + + +.. method:: mutex.testandset() + + "Atomic" test-and-set, grab the lock if it is not set, and return ``True``, + otherwise, return ``False``. + + +.. method:: mutex.lock(function, argument) + + Execute ``function(argument)``, unless the mutex is locked. In the case it is + locked, place the function and argument on the queue. See :meth:`unlock` for + explanation of when ``function(argument)`` is executed in that case. + + +.. method:: mutex.unlock() + + Unlock the mutex if queue is empty, otherwise execute the first element in the + queue. + |