What is the difference between Lock and RLock
Solution 1
The main difference is that a Lock
can only be acquired once. It cannot be acquired again, until it is released. (After it's been released, it can be re-acaquired by any thread).
An RLock
on the other hand, can be acquired multiple times, by the same thread. It needs to be released the same number of times in order to be "unlocked".
Another difference is that an acquired Lock
can be released by any thread, while an acquired RLock
can only be released by the thread which acquired it.
Here's an example demostrating why RLock
is useful at times. Suppose you have:
def f():
g()
h()
def g():
h()
do_something1()
def h():
do_something2()
Let's say all of f
, g
, and h
are public (i.e. can be called directly by an external caller), and all of them require syncronization.
Using a Lock
, you can do something like:
lock = Lock()
def f():
with lock:
_g()
_h()
def g():
with lock:
_g()
def _g():
_h()
do_something1()
def h():
with lock:
_h()
def _h():
do_something2()
Basically, since f
cannot call g
after acquiring the lock, it needs to call a "raw" version of g
(i.e. _g
). So you end up with a "synced" version and a "raw" version of each function.
Using an RLock
elegantly solves the problem:
lock = RLock()
def f():
with lock:
g()
h()
def g():
with lock:
h()
do_something1()
def h():
with lock:
do_something2()
Solution 2
To expand on shx2's answer, the reason why you want to use one vs the other might be the following:
A regular Lock
(mutex) is typically faster and safer.
The reason for using RLock
is to avoid a dead lock due to e.g. recursion. For instance, let's put a lock in the recursive factorial function. (admittedly somewhat contrived)
from threading import Lock
lock = Lock()
def factorial(n):
assert n > 0
if n == 1:
return 1
with lock:
out = n * factorial(n - 1)
return out
This function will cause a dead lock due to the recursive call. If we use RLock
instead, however, the recursive calls can reenter the same lock as many times as needed. Hence the name reentrant (or recursive) lock.
BufBills
Updated on August 06, 2020Comments
-
BufBills almost 4 years
From the docs:
threading.RLock() -- A factory function that returns a new reentrant lock object. A reentrant lock must be released by the thread that acquired it. Once a thread has acquired a reentrant lock, the same thread may acquire it again without blocking; the thread must release it once for each time it has acquired it.
I am not sure why do we need this? what's the difference between
Rlock
andLock
? -
Mateen Ulhaq over 5 yearsIs there ever any practical "benefit" to using
Lock
, then? -
shx2 over 5 years@MateenUlhaq, yes.
Lock
operations are fastser. -
PirateApp about 5 yearssorry if this is a stupid question but why would I want to acquire a lock multiple times, if I need to increment a counter I simply acquire a Lock() and release it , why do we need a counter on it to keep incrementing or decrementing
-
Erik Aronesty almost 5 years@PirateApp suppose you acquire a granular lock (ie: on a file) and do something fairly expensive (ie: decrypting it). an rlock prevents deadlocks from forming in a complex series of dependencies that, also, may try to acquire the same lock.
-
Valentyn almost 5 years@MateenUlhaq I apologize. I have read this comment "@MateenUlhaq, yes. Lock operations are fastser. – shx2 Nov 22 '18 at 18:11" and completely missed it was by shx2 not by you. My colleague used to use Lock() but I have found RLock() and is looks much better and safer. So I did wonder the same: Why would anyone use Lock()?
-
Jamaica-Jan almost 4 yearsthink you want
if n ==1: return 1
-
Kris almost 4 yearsYou're right, I updated the logic to start with the non-recursive branch.
-
Torsten Bronger over 3 years@ErikAronesty You avoid a deadlock by simply bypassing the lock?
-
Erik Aronesty over 3 years@TorstenBronger an rlock allows the same thread to re-enter the function, which is, often, not something you need to protect against. especially if the lock is protecting an o/s resource, or s sqlite handle, etc
-
Alperen Sözer almost 3 yearsen.wikipedia.org/wiki/Reentrant_mutex -> In computer science, the reentrant mutex (recursive mutex, recursive lock) is a particular type of mutual exclusion (mutex) device that may be locked multiple times by the same process/thread, without causing a deadlock.