Skip to content

Define accelerator capability model and fallback policy #26

@Tinnci

Description

@Tinnci

Define the cross-backend accelerator model before adding provider-specific code.

Scope:

  • Separate logical device selection (cpu, cuda, rocm, xpu, mps, directml, auto) from backend implementation (self_torch, self_onnx, external_package, external_sdk).
  • Extend capability metadata without making every backend import heavy runtimes at listing time.
  • Define fallback behavior when a requested accelerator is unavailable.
  • Keep default CPU/offline behavior deterministic.

Acceptance criteria:

  • --list-models / --list-backends can report accelerator support clearly.
  • device=auto behavior is documented and testable.
  • Unsupported requested accelerators fail with actionable errors.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions