-
Notifications
You must be signed in to change notification settings - Fork 12.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DOC] Improve the thread::park and thread::unpark documentation #41809
Changes from 7 commits
061b56b
c158962
d9628f9
5573c47
c0d475a
fa0cdaa
03c9510
afe74c3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -96,41 +96,6 @@ | |
//! The [`thread::current`] function is available even for threads not spawned | ||
//! by the APIs of this module. | ||
//! | ||
//! ## Blocking support: park and unpark | ||
//! | ||
//! Every thread is equipped with some basic low-level blocking support, via the | ||
//! [`thread::park`][`park`] function and [`thread::Thread::unpark()`][`unpark`] | ||
//! method. [`park`] blocks the current thread, which can then be resumed from | ||
//! another thread by calling the [`unpark`] method on the blocked thread's handle. | ||
//! | ||
//! Conceptually, each [`Thread`] handle has an associated token, which is | ||
//! initially not present: | ||
//! | ||
//! * The [`thread::park`][`park`] function blocks the current thread unless or until | ||
//! the token is available for its thread handle, at which point it atomically | ||
//! consumes the token. It may also return *spuriously*, without consuming the | ||
//! token. [`thread::park_timeout`] does the same, but allows specifying a | ||
//! maximum time to block the thread for. | ||
//! | ||
//! * The [`unpark`] method on a [`Thread`] atomically makes the token available | ||
//! if it wasn't already. | ||
//! | ||
//! In other words, each [`Thread`] acts a bit like a semaphore with initial count | ||
//! 0, except that the semaphore is *saturating* (the count cannot go above 1), | ||
//! and can return spuriously. | ||
//! | ||
//! The API is typically used by acquiring a handle to the current thread, | ||
//! placing that handle in a shared data structure so that other threads can | ||
//! find it, and then `park`ing. When some desired condition is met, another | ||
//! thread calls [`unpark`] on the handle. | ||
//! | ||
//! The motivation for this design is twofold: | ||
//! | ||
//! * It avoids the need to allocate mutexes and condvars when building new | ||
//! synchronization primitives; the threads already provide basic blocking/signaling. | ||
//! | ||
//! * It can be implemented very efficiently on many platforms. | ||
//! | ||
//! ## Thread-local storage | ||
//! | ||
//! This module also provides an implementation of thread-local storage for Rust | ||
|
@@ -547,23 +512,72 @@ pub fn sleep(dur: Duration) { | |
|
||
/// Blocks unless or until the current thread's token is made available. | ||
/// | ||
/// Every thread is equipped with some basic low-level blocking support, via | ||
/// the `park()` function and the [`unpark`][unpark] method. These can be | ||
/// used as a more CPU-efficient implementation of a spinlock. | ||
/// A call to `park` does not guarantee that the thread will remain parked | ||
/// forever, and callers should be prepared for this possibility. | ||
/// | ||
/// # park and unpark | ||
/// | ||
/// Every thread is equipped with some basic low-level blocking support, via the | ||
/// [`thread::park`][`park`] function and [`thread::Thread::unpark`][`unpark`] | ||
/// method. [`park`] blocks the current thread, which can then be resumed from | ||
/// another thread by calling the [`unpark`] method on the blocked thread's | ||
/// handle. | ||
/// | ||
/// Conceptually, each [`Thread`] handle has an associated token, which is | ||
/// initially not present: | ||
/// | ||
/// [unpark]: struct.Thread.html#method.unpark | ||
/// * The [`thread::park`][`park`] function blocks the current thread unless or | ||
/// until the token is available for its thread handle, at which point it | ||
/// atomically consumes the token. It may also return *spuriously*, without | ||
/// consuming the token. [`thread::park_timeout`] does the same, but allows | ||
/// specifying a maximum time to block the thread for. | ||
/// | ||
/// * The [`unpark`] method on a [`Thread`] atomically makes the token available | ||
/// if it wasn't already. | ||
/// | ||
/// In other words, each [`Thread`] acts a bit like a spinlock that can be | ||
/// locked and unlocked using `park` and `unpark`. | ||
/// | ||
/// The API is typically used by acquiring a handle to the current thread, | ||
/// placing that handle in a shared data structure so that other threads can | ||
/// find it, and then parking (in a loop with a check for the token actually | ||
/// being acquired). | ||
/// find it, and then `park`ing. When some desired condition is met, another | ||
/// thread calls [`unpark`] on the handle. | ||
/// | ||
/// A call to `park` does not guarantee that the thread will remain parked | ||
/// forever, and callers should be prepared for this possibility. | ||
/// The motivation for this design is twofold: | ||
/// | ||
/// * It avoids the need to allocate mutexes and condvars when building new | ||
/// synchronization primitives; the threads already provide basic | ||
/// blocking/signaling. | ||
/// | ||
/// See the [module documentation][thread] for more detail. | ||
/// * It can be implemented very efficiently on many platforms. | ||
/// | ||
/// [thread]: index.html | ||
/// # Examples | ||
/// | ||
/// ``` | ||
/// use std::thread; | ||
/// use std::time::Duration; | ||
/// | ||
/// let parked_thread = thread::Builder::new() | ||
/// .spawn(|| { | ||
/// println!("Parking thread"); | ||
/// thread::park(); | ||
/// println!("Thread unparked"); | ||
/// }) | ||
/// .unwrap(); | ||
/// | ||
/// // Let some time pass for the thread to be spawned. | ||
/// thread::sleep(Duration::from_millis(10)); | ||
/// | ||
/// println!("Unpark the thread"); | ||
/// parked_thread.thread().unpark(); | ||
/// | ||
/// parked_thread.join().unwrap(); | ||
/// ``` | ||
/// | ||
/// [`Thread`]: ../../std/thread/struct.Thread.html | ||
/// [`park`]: ../../std/thread/fn.park.html | ||
/// [`unpark`]: ../../std/thread/struct.Thread.html#method.unpark | ||
/// [`thread::park_timeout`]: ../../std/thread/fn.park_timeout.html | ||
// | ||
// The implementation currently uses the trivial strategy of a Mutex+Condvar | ||
// with wakeup flag, which does not actually allow spurious wakeups. In the | ||
|
@@ -585,16 +599,16 @@ pub fn park() { | |
/// Blocks unless or until the current thread's token is made available or | ||
/// the specified duration has been reached (may wake spuriously). | ||
/// | ||
/// The semantics of this function are equivalent to `park()` except that the | ||
/// thread will be blocked for roughly no longer than `ms`. This method | ||
/// should not be used for precise timing due to anomalies such as | ||
/// The semantics of this function are equivalent to [`park`][park] except | ||
/// that the thread will be blocked for roughly no longer than `dur`. This | ||
/// method should not be used for precise timing due to anomalies such as | ||
/// preemption or platform differences that may not cause the maximum | ||
/// amount of time waited to be precisely `ms` long. | ||
/// | ||
/// See the [module documentation][thread] for more detail. | ||
/// See the [park documentation][park] for more detail. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The link should point to There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Indeed, missed that one. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this still needs to be fixed There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Done :) |
||
/// | ||
/// [thread]: index.html | ||
/// [park_timeout]: fn.park_timeout.html | ||
/// [park]: ../../std/thread/fn.park.html | ||
#[stable(feature = "rust1", since = "1.0.0")] | ||
#[rustc_deprecated(since = "1.6.0", reason = "replaced by `std::thread::park_timeout`")] | ||
pub fn park_timeout_ms(ms: u32) { | ||
|
@@ -604,13 +618,13 @@ pub fn park_timeout_ms(ms: u32) { | |
/// Blocks unless or until the current thread's token is made available or | ||
/// the specified duration has been reached (may wake spuriously). | ||
/// | ||
/// The semantics of this function are equivalent to `park()` except that the | ||
/// thread will be blocked for roughly no longer than `dur`. This method | ||
/// should not be used for precise timing due to anomalies such as | ||
/// The semantics of this function are equivalent to [`park`][park] except | ||
/// that the thread will be blocked for roughly no longer than `dur`. This | ||
/// method should not be used for precise timing due to anomalies such as | ||
/// preemption or platform differences that may not cause the maximum | ||
/// amount of time waited to be precisely `dur` long. | ||
/// | ||
/// See the module doc for more detail. | ||
/// See the [park dococumentation][park] for more details. | ||
/// | ||
/// # Platform behavior | ||
/// | ||
|
@@ -635,6 +649,8 @@ pub fn park_timeout_ms(ms: u32) { | |
/// park_timeout(timeout); | ||
/// } | ||
/// ``` | ||
/// | ||
/// [park]: fn.park.html | ||
#[stable(feature = "park_timeout", since = "1.4.0")] | ||
pub fn park_timeout(dur: Duration) { | ||
let thread = current(); | ||
|
@@ -764,22 +780,36 @@ impl Thread { | |
|
||
/// Atomically makes the handle's token available if it is not already. | ||
/// | ||
/// See the module doc for more detail. | ||
/// Every thread is equipped with some basic low-level blocking support, via | ||
/// the [`park`][park] function and the `unpark()` method. These can be | ||
/// used as a more CPU-efficient implementation of a spinlock. | ||
/// | ||
/// See the [park documentation][park] for more details. | ||
/// | ||
/// # Examples | ||
/// | ||
/// ``` | ||
/// use std::thread; | ||
/// use std::time::Duration; | ||
/// | ||
/// let handler = thread::Builder::new() | ||
/// let parked_thread = thread::Builder::new() | ||
/// .spawn(|| { | ||
/// let thread = thread::current(); | ||
/// thread.unpark(); | ||
/// println!("Parking thread"); | ||
/// thread::park(); | ||
/// println!("Thread unparked"); | ||
/// }) | ||
/// .unwrap(); | ||
/// | ||
/// handler.join().unwrap(); | ||
/// // Let some time pass for the thread to be spawned. | ||
/// thread::sleep(Duration::from_millis(10)); | ||
/// | ||
/// println!("Unpark the thread"); | ||
/// parked_thread.thread().unpark(); | ||
/// | ||
/// parked_thread.join().unwrap(); | ||
/// ``` | ||
/// | ||
/// [park]: fn.park.html | ||
#[stable(feature = "rust1", since = "1.0.0")] | ||
pub fn unpark(&self) { | ||
let mut guard = self.inner.lock.lock().unwrap(); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per the failures on Travis (scroll near the bottom), you'll need to import
Duration
into scope hereThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(this has been addressed)