1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315
//! Contains support for user-managed thread pools, represented by the //! the [`ThreadPool`] type (see that struct for details). //! //! [`ThreadPool`]: struct.ThreadPool.html use crate::join; use crate::registry::{Registry, ThreadSpawn, WorkerThread}; use crate::spawn; #[allow(deprecated)] use crate::Configuration; use crate::{scope, Scope}; use crate::{scope_fifo, ScopeFifo}; use crate::{ThreadPoolBuildError, ThreadPoolBuilder}; use std::error::Error; use std::fmt; use std::sync::Arc; mod test; /// Represents a user created [thread-pool]. /// /// Use a [`ThreadPoolBuilder`] to specify the number and/or names of threads /// in the pool. After calling [`ThreadPoolBuilder::build()`], you can then /// execute functions explicitly within this [`ThreadPool`] using /// [`ThreadPool::install()`]. By contrast, top level rayon functions /// (like `join()`) will execute implicitly within the current thread-pool. /// /// /// ## Creating a ThreadPool /// /// ```rust /// # use rayon_core as rayon; /// let pool = rayon::ThreadPoolBuilder::new().num_threads(8).build().unwrap(); /// ``` /// /// [`install()`][`ThreadPool::install()`] executes a closure in one of the `ThreadPool`'s /// threads. In addition, any other rayon operations called inside of `install()` will also /// execute in the context of the `ThreadPool`. /// /// When the `ThreadPool` is dropped, that's a signal for the threads it manages to terminate, /// they will complete executing any remaining work that you have spawned, and automatically /// terminate. /// /// /// [thread-pool]: https://en.wikipedia.org/wiki/Thread_pool /// [`ThreadPool`]: struct.ThreadPool.html /// [`ThreadPool::new()`]: struct.ThreadPool.html#method.new /// [`ThreadPoolBuilder`]: struct.ThreadPoolBuilder.html /// [`ThreadPoolBuilder::build()`]: struct.ThreadPoolBuilder.html#method.build /// [`ThreadPool::install()`]: struct.ThreadPool.html#method.install pub struct ThreadPool { registry: Arc<Registry>, } impl ThreadPool { #[deprecated(note = "Use `ThreadPoolBuilder::build`")] #[allow(deprecated)] /// Deprecated in favor of `ThreadPoolBuilder::build`. pub fn new(configuration: Configuration) -> Result<ThreadPool, Box<dyn Error>> { Self::build(configuration.into_builder()).map_err(Box::from) } pub(super) fn build<S>( builder: ThreadPoolBuilder<S>, ) -> Result<ThreadPool, ThreadPoolBuildError> where S: ThreadSpawn, { let registry = Registry::new(builder)?; Ok(ThreadPool { registry }) } /// Executes `op` within the threadpool. Any attempts to use /// `join`, `scope`, or parallel iterators will then operate /// within that threadpool. /// /// # Warning: thread-local data /// /// Because `op` is executing within the Rayon thread-pool, /// thread-local data from the current thread will not be /// accessible. /// /// # Panics /// /// If `op` should panic, that panic will be propagated. /// /// ## Using `install()` /// /// ```rust /// # use rayon_core as rayon; /// fn main() { /// let pool = rayon::ThreadPoolBuilder::new().num_threads(8).build().unwrap(); /// let n = pool.install(|| fib(20)); /// println!("{}", n); /// } /// /// fn fib(n: usize) -> usize { /// if n == 0 || n == 1 { /// return n; /// } /// let (a, b) = rayon::join(|| fib(n - 1), || fib(n - 2)); // runs inside of `pool` /// return a + b; /// } /// ``` pub fn install<OP, R>(&self, op: OP) -> R where OP: FnOnce() -> R + Send, R: Send, { self.registry.in_worker(|_, _| op()) } /// Returns the (current) number of threads in the thread pool. /// /// # Future compatibility note /// /// Note that unless this thread-pool was created with a /// [`ThreadPoolBuilder`] that specifies the number of threads, /// then this number may vary over time in future versions (see [the /// `num_threads()` method for details][snt]). /// /// [snt]: struct.ThreadPoolBuilder.html#method.num_threads /// [`ThreadPoolBuilder`]: struct.ThreadPoolBuilder.html #[inline] pub fn current_num_threads(&self) -> usize { self.registry.num_threads() } /// If called from a Rayon worker thread in this thread-pool, /// returns the index of that thread; if not called from a Rayon /// thread, or called from a Rayon thread that belongs to a /// different thread-pool, returns `None`. /// /// The index for a given thread will not change over the thread's /// lifetime. However, multiple threads may share the same index if /// they are in distinct thread-pools. /// /// # Future compatibility note /// /// Currently, every thread-pool (including the global /// thread-pool) has a fixed number of threads, but this may /// change in future Rayon versions (see [the `num_threads()` method /// for details][snt]). In that case, the index for a /// thread would not change during its lifetime, but thread /// indices may wind up being reused if threads are terminated and /// restarted. /// /// [snt]: struct.ThreadPoolBuilder.html#method.num_threads #[inline] pub fn current_thread_index(&self) -> Option<usize> { let curr = self.registry.current_thread()?; Some(curr.index()) } /// Returns true if the current worker thread currently has "local /// tasks" pending. This can be useful as part of a heuristic for /// deciding whether to spawn a new task or execute code on the /// current thread, particularly in breadth-first /// schedulers. However, keep in mind that this is an inherently /// racy check, as other worker threads may be actively "stealing" /// tasks from our local deque. /// /// **Background:** Rayon's uses a [work-stealing] scheduler. The /// key idea is that each thread has its own [deque] of /// tasks. Whenever a new task is spawned -- whether through /// `join()`, `Scope::spawn()`, or some other means -- that new /// task is pushed onto the thread's *local* deque. Worker threads /// have a preference for executing their own tasks; if however /// they run out of tasks, they will go try to "steal" tasks from /// other threads. This function therefore has an inherent race /// with other active worker threads, which may be removing items /// from the local deque. /// /// [work-stealing]: https://en.wikipedia.org/wiki/Work_stealing /// [deque]: https://en.wikipedia.org/wiki/Double-ended_queue #[inline] pub fn current_thread_has_pending_tasks(&self) -> Option<bool> { let curr = self.registry.current_thread()?; Some(!curr.local_deque_is_empty()) } /// Execute `oper_a` and `oper_b` in the thread-pool and return /// the results. Equivalent to `self.install(|| join(oper_a, /// oper_b))`. pub fn join<A, B, RA, RB>(&self, oper_a: A, oper_b: B) -> (RA, RB) where A: FnOnce() -> RA + Send, B: FnOnce() -> RB + Send, RA: Send, RB: Send, { self.install(|| join(oper_a, oper_b)) } /// Creates a scope that executes within this thread-pool. /// Equivalent to `self.install(|| scope(...))`. /// /// See also: [the `scope()` function][scope]. /// /// [scope]: fn.scope.html pub fn scope<'scope, OP, R>(&self, op: OP) -> R where OP: FnOnce(&Scope<'scope>) -> R + Send, R: Send, { self.install(|| scope(op)) } /// Creates a scope that executes within this thread-pool. /// Spawns from the same thread are prioritized in relative FIFO order. /// Equivalent to `self.install(|| scope_fifo(...))`. /// /// See also: [the `scope_fifo()` function][scope_fifo]. /// /// [scope_fifo]: fn.scope_fifo.html pub fn scope_fifo<'scope, OP, R>(&self, op: OP) -> R where OP: FnOnce(&ScopeFifo<'scope>) -> R + Send, R: Send, { self.install(|| scope_fifo(op)) } /// Spawns an asynchronous task in this thread-pool. This task will /// run in the implicit, global scope, which means that it may outlast /// the current stack frame -- therefore, it cannot capture any references /// onto the stack (you will likely need a `move` closure). /// /// See also: [the `spawn()` function defined on scopes][spawn]. /// /// [spawn]: struct.Scope.html#method.spawn pub fn spawn<OP>(&self, op: OP) where OP: FnOnce() + Send + 'static, { // We assert that `self.registry` has not terminated. unsafe { spawn::spawn_in(op, &self.registry) } } /// Spawns an asynchronous task in this thread-pool. This task will /// run in the implicit, global scope, which means that it may outlast /// the current stack frame -- therefore, it cannot capture any references /// onto the stack (you will likely need a `move` closure). /// /// See also: [the `spawn_fifo()` function defined on scopes][spawn_fifo]. /// /// [spawn_fifo]: struct.ScopeFifo.html#method.spawn_fifo pub fn spawn_fifo<OP>(&self, op: OP) where OP: FnOnce() + Send + 'static, { // We assert that `self.registry` has not terminated. unsafe { spawn::spawn_fifo_in(op, &self.registry) } } } impl Drop for ThreadPool { fn drop(&mut self) { self.registry.terminate(); } } impl fmt::Debug for ThreadPool { fn fmt(&self, fmt: &mut fmt::Formatter<'_>) -> fmt::Result { fmt.debug_struct("ThreadPool") .field("num_threads", &self.current_num_threads()) .field("id", &self.registry.id()) .finish() } } /// If called from a Rayon worker thread, returns the index of that /// thread within its current pool; if not called from a Rayon thread, /// returns `None`. /// /// The index for a given thread will not change over the thread's /// lifetime. However, multiple threads may share the same index if /// they are in distinct thread-pools. /// /// See also: [the `ThreadPool::current_thread_index()` method]. /// /// [m]: struct.ThreadPool.html#method.current_thread_index /// /// # Future compatibility note /// /// Currently, every thread-pool (including the global /// thread-pool) has a fixed number of threads, but this may /// change in future Rayon versions (see [the `num_threads()` method /// for details][snt]). In that case, the index for a /// thread would not change during its lifetime, but thread /// indices may wind up being reused if threads are terminated and /// restarted. /// /// [snt]: struct.ThreadPoolBuilder.html#method.num_threads #[inline] pub fn current_thread_index() -> Option<usize> { unsafe { let curr = WorkerThread::current().as_ref()?; Some(curr.index()) } } /// If called from a Rayon worker thread, indicates whether that /// thread's local deque still has pending tasks. Otherwise, returns /// `None`. For more information, see [the /// `ThreadPool::current_thread_has_pending_tasks()` method][m]. /// /// [m]: struct.ThreadPool.html#method.current_thread_has_pending_tasks #[inline] pub fn current_thread_has_pending_tasks() -> Option<bool> { unsafe { let curr = WorkerThread::current().as_ref()?; Some(!curr.local_deque_is_empty()) } }