Guides loading, evaluating, and rolling out SPCX congestion-control algorithms on BlueField DPAs.
npx skills add https://github.com/NVIDIA/skills --skill doca-spcx-cc
Please help me install this Agent Skill. Skill: doca-spcx-cc Source: https://github.com/NVIDIA/skills/tree/main/skills/doca-spcx-cc Command: npx skills add https://github.com/NVIDIA/skills --skill doca-spcx-cc
Deploying a custom Programmable Congestion Control algorithm on a live RDMA / RoCE fabric is high-stakes: a wrong or unstable algorithm can cause flow collapse, queue blow-up, or fabric-wide instability, and an idle-link evaluation produces no meaningful signal. This Skill gives agents the operator-side discipline for the doca_spcx_cc CLI so SPCX algorithms are loaded, evaluated under real contention, and rolled forward only with evidence and a rehearsed rollback.
doca-pcc surface, and factory firmware PCC before any code is written, based on install, BlueField generation, and algorithm needs.doca_spcx_cc, injecting matching contention, capturing the evidence tuple, and deciding whether it is safe to roll forward.Ask your agent to load and evaluate your DPACC-compiled SPCX congestion-control algorithm on a non-production BlueField pair using doca_spcx_cc, with contention injected and a documented rollback to factory PCC.
High-intent search queries and answers about installing and using this skill.
Compile the DPA-side algorithm image with a DPACC version matched to your DOCA install, then invoke doca_spcx_cc with the device, probe-packet format, and algorithm-image flags shown by --help. Confirm the host-side status reaches Active before drawing any conclusions.
SPCX is the newer, more flexible programmable-CC extension, while doca-pcc is the stable established surface and factory PCC is the firmware-resident default needing no host code. Probe your install with doca_spcx_cc --help and the public DOCA SPCX guide before committing, since SPCX availability is install- and hardware-specific.
A congestion-control algorithm has no observable signal without actual contention on the fabric. Confirm the link carries RDMA / RoCE traffic with contention matching the algorithm's design, verified via PCC counter snapshots, before concluding the algorithm is broken.
No. On DOCA 3.3 the shipped reference sample hard-codes cfg.role = PCC_ROLE_RP in pcc.c and registers no runtime --role flag. To run the Notification Point role, rebuild the sample with PCC_ROLE_NP or follow the public DOCA SPCX guide for your installed version.
The rollout gate requires replica-first evaluation matching production hardware and contention, two consistent runs, a bounded blast-radius plan starting with one BlueField pair, a rehearsed rollback to factory PCC, reachable out-of-band management, and a time-boxed maintenance window. Any failed gate blocks the cutover.
It maps to the layered error taxonomy: check install, device binding, firmware custom-PCC slot enablement, DPA-image and DPACC version pairing, and algorithm preconditions in order. Walk each layer rather than guessing, and verify the tool, doca-pcc library, DPACC, and firmware versions all match.
robertsthomasAutomate LaunchDarkly SDK onboarding with dependency installation, environment configuration, and compile verification.
hollis-labsRefresh Project Context Cache files with minimal diffs from git changes or explicit scope values.
air-gappedAutomate NVIDIA datacenter GPU bring-up on Ubuntu 24.04 with health validation.
UnaMentisConfigure MCP session defaults for iOS and USM environments.