What problem does it solve?
Building an NVMe-over-Fabrics target that offloads the data path to a BlueField DPU with DOCA STA involves a strict lifecycle, capability queries, queue-pair sizing, RDMA transport setup, and a layered error taxonomy that is easy to get wrong. This Skill gives an AI agent the exact workflows and guardrails to configure, build, run, test, and debug doca_sta-based targets without hallucinating API symbols or sizing values.
Core Features & Use Cases
- Target configuration workflows: Step-by-step guidance for creating a doca_sta context, defining doca_sta_subsystem targets (NQN + namespaces) backed by local NVMe-PCI disks (doca_sta_be), and gating every sizing decision on doca_sta_cap_is_supported and the doca_sta_get_max_* queries.
- Build and version validation: Canonical pkg-config build pattern linking doca-sta plus the mandatory doca-rdma substrate, with four-way version-match checks against doca_caps --version to catch partial installs.
- Layered debugging and testing: An iterative test loop (capability re-check, substrate/steering preconditions, single-IO admin-then-read smoke, multi-queue smoke) and a debug ladder that maps DOCA_ERROR_* codes to the correct layer before any code change.
- Use Case: A developer asks why their NVMe-oF Connect handshake never completes; the agent loads this Skill, walks the substrate/steering precondition matrix, and identifies a missing DOCA Flow steering rule rather than misdiagnosing a STA bug.
Quick Start
Ask your agent to help you bring up an NVMe-oF target on a BlueField DPU using DOCA STA, for example by saying "help me configure a doca_sta subsystem backed by a local NVMe disk and verify my device supports it".