axiolid-dispatch 0.3.0

Provider registration, ordering, fallback, and execution policy
Documentation 
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

//! Device preference matching, shared by every operation registry.
//!
//! One implementation so a new operation cannot drift from the established
//! routing semantics: adding a registry that quietly treats `Cpu` as
//! portable-only would silently exclude optimised backends.

use axiolid_contracts::{BackendId, DevicePreference, ExecutionTarget};

/// Whether a backend satisfies the caller's device preference.
pub(crate) fn matches_device(
    preference: DevicePreference,
    id: BackendId,
    target: ExecutionTarget,
) -> bool {
    match preference {
        DevicePreference::Auto => true,
        DevicePreference::Cpu => {
            matches!(
                target,
                ExecutionTarget::PortableCpu | ExecutionTarget::OptimizedCpu
            )
        }
        DevicePreference::Gpu => matches!(target, ExecutionTarget::Gpu),
        DevicePreference::Backend(required) => required == id,
    }
}