[−][src]Module fast_async_mutex::rwlock_ordered
The RW Lock mechanism accepts you get shared access to your data without locking. The Ordered RW Lock will be locking all reads, which starting after write and unlocking them only when write will realize. It may be slow down the reads speed, but decrease time to write on systems, where it is critical.
BUT RW Lock has some limitations. You should avoid acquiring the second reading before realizing first inside the one future. Because it can happen that between your readings a write from another thread will acquire the mutex, and you will get a deadlock.
Structs
OrderedRwLock | The Ordered RW Lock will be locking all reads, which starting after write and unlocking them only when write will realize. It may be slow down the reads speed, but decrease time to write on systems, where it is critical. |
OrderedRwLockReadGuard | The Simple Write Lock Guard
As long as you have this guard, you have shared access to the underlying |
OrderedRwLockReadGuardFuture | |
OrderedRwLockReadOwnedGuard | An owned handle to a held RWLock.
This guard is only available from a RWLock that is wrapped in an |
OrderedRwLockReadOwnedGuardFuture | |
OrderedRwLockWriteGuard | The Simple Write Lock Guard
As long as you have this guard, you have exclusive access to the underlying |
OrderedRwLockWriteGuardFuture | |
OrderedRwLockWriteOwnedGuard | An owned handle to a held RWLock.
This guard is only available from a RWLock that is wrapped in an |
OrderedRwLockWriteOwnedGuardFuture |