Crates.io | sortlock |
lib.rs | sortlock |
version | 0.2.0 |
source | src |
created_at | 2024-03-27 11:15:57.895368 |
updated_at | 2024-08-18 13:20:23.309196 |
description | A crate providing ordered locking. |
homepage | https://crates.io/crates/sortlock |
repository | https://github.com/WhyAreAllTheseTaken/sortlock |
max_upload_size | |
id | 1187807 |
size | 33,060 |
A crate providing ordered locking. That is locks that will always lock in the same order regardless of the order in which the methods are called. This reduces deadlocks caused by cycles as one lock waits for another. In particular the following case cannot happen when exclusively using lock sorting:
lock1
.lock2
.lock2
but it is locked by thread B.lock1
but it is locked by thread A.With lock sorting this cannot occur as locks are always locked in the same order for both
threads. This is done by first requesting to lock each lock. Then, by placing the locks in a
tuple and calling the lock_all
method, the locks will be locked in the same order regardless
of their order in the tuple.
To allow for sorted locking, this crates provides two new types of lock:
SortMuted
- A sorted version of Mutex
.SortRwLock
- A sorted version of RwLock
.use sortlock::{SortMutex, LockGroup};
let lock1 = SortMutex::new("some value");
let lock2 = SortMutex::new("some other value");
// Here lock1 is locked then lock2.
let (guard1, guard2) = (lock1.lock(), lock2.lock()).lock_all();
println!("{}", *guard1);
println!("{}", *guard2);
// Unlock so we can lock again.
drop(guard1);
drop(guard2);
// Despite the order change the same is true here.
let (guard2, guard1) = (lock2.lock(), lock1.lock()).lock_all();
println!("{}", *guard1);
println!("{}", *guard2);
To support no-std
environments this crate can fall back to using spin
's Mutex
and RwLock
types. This can be done by disabiling the std
feature.