pub enum ExecutionPolicy {
AmbientRayon,
Sequential,
Rayon {
max_threads: NonZeroUsize,
},
}Expand description
Controls how a strided operation may use CPU threads.
This policy controls fanout only. It does not create a Rayon pool or choose
CPU placement; callers that need placement control should install the
operation in their chosen executor and then select Self::Sequential or
Self::Rayon.
The policy applies to fanout owned by strided-kernel. A bounded worker
partition runs nested strided operations sequentially so nested operations
cannot multiply the outer budget. The scope is worker-local, not a
task-local Rayon context, and is not propagated to threads or Rayon tasks
created by user callbacks.
User callbacks that rely on policy isolation must not enter their own Rayon
scheduling or yield boundary (join, scope, spawn, and similar APIs).
At such a callback-owned boundary, Rayon may execute unrelated work on the
waiting worker while its worker-local policy is active. strided-kernel
suspends the policy at every scheduler boundary it owns, but cannot do so
for arbitrary scheduling performed inside a callback.
Variants§
AmbientRayon
Preserve the compatibility behavior of using all threads in the current installed Rayon pool, or the global pool when no pool is installed.
Explicit runtimes should prefer Self::Sequential or Self::Rayon.
Sequential
Execute entirely on the calling thread with zero Rayon fanout.
Rayon
Use the currently installed Rayon pool while limiting the operation to
at most max_threads concurrent partitions.
Without the parallel feature, operations remain sequential.
Fields
max_threads: NonZeroUsizeTrait Implementations§
Source§impl Clone for ExecutionPolicy
impl Clone for ExecutionPolicy
Source§fn clone(&self) -> ExecutionPolicy
fn clone(&self) -> ExecutionPolicy
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more