commit | 1a790eb5ab83270ae68fda977fe72d5b00d5629b | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Jun 15 21:45:36 2022 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Jun 15 21:45:36 2022 +0000 |
tree | 8aa33bfe69d31d520c9f1aa0b31ed2e4683f5595 | |
parent | abe3eeedd93ce8931ecb6d1186c2861682d5f03b [diff] | |
parent | 46303a78f20e28e8c381dfa18132a87863e0895b [diff] |
Snap for 8730993 from 46303a78f20e28e8c381dfa18132a87863e0895b to mainline-tzdata3-release Change-Id: I097b521a652f6fcc62a309cf2ec115cc739ec266
Spin-based synchronization primitives.
This crate provides spin-based versions of the primitives in std::sync
. Because synchronization is done through spinning, the primitives are suitable for use in no_std
environments.
Before deciding to use spin
, we recommend reading this superb blog post by @matklad that discusses the pros and cons of spinlocks. If you have access to std
, it's likely that the primitives in std::sync
will serve you better except in very specific circumstances.
Mutex
, RwLock
and Once
equivalentsno_std
environmentslock_api
compatibilityRwLock
guardsstd
feature to enable yield to the OS scheduler in busy loopsMutex
can become a ticket lockInclude the following under the [dependencies]
section in your Cargo.toml
file.
spin = "x.y"
When calling lock
on a Mutex
you will get a guard value that provides access to the data. When this guard is dropped, the lock will be unlocked.
extern crate spin; use std::{sync::Arc, thread}; fn main() { let counter = Arc::new(spin::Mutex::new(0)); let thread = thread::spawn({ let counter = counter.clone(); move || { for _ in 0..10 { *counter.lock() += 1; } } }); for _ in 0..10 { *counter.lock() += 1; } thread.join().unwrap(); assert_eq!(*counter.lock(), 20); }
The crate comes with a few feature flags that you may wish to use.
lock_api
enabled support for lock_api
ticket_mutex
uses a ticket lock for the implementation of Mutex
std
enables support for thread yielding instead of spinning
It is often desirable to have a lock shared between threads. Wrapping the lock in an std::sync::Arc
is route through which this might be achieved.
Locks provide zero-overhead access to their data when accessed through a mutable reference by using their get_mut
methods.
The behaviour of these lock is similar to their namesakes in std::sync
. they differ on the following:
spin
is distributed under the MIT License, (See LICENSE
).