Arm and read firmware PCC diagnostic counters on ConnectX and BlueField devices.
npx skills add https://github.com/NVIDIA/skills --skill doca-pcc-counters
Please help me install this Agent Skill. Skill: doca-pcc-counters Source: https://github.com/NVIDIA/skills/tree/main/skills/doca-pcc-counters Command: npx skills add https://github.com/NVIDIA/skills --skill doca-pcc-counters
Reading a ConnectX or BlueField device's firmware PCC (Programmable Congestion Control) diagnostic counters requires knowing the exact two-operation contract of the pcc_counters.sh script, the mst device resolution flow, and the mlx5 debugfs diag_cnt interface, and mistakes like querying before arming or misreading a zero counter lead to wrong congestion-control conclusions.
Ask your agent to arm and read the PCC diagnostic counters on your device, for example: "Use pcc_counters.sh to set and then query the PCC counters on /dev/mst/mt41692_pciconf0 and show me the CNP and WRED-drop values."
High-intent search queries and answers about installing and using this skill.
Run sudo ./pcc_counters.sh set <mst-device> first to arm the counters, then sudo ./pcc_counters.sh query <mst-device> to read them. The device argument must be an mst path from sudo mst status -v, such as /dev/mst/mt41692_pciconf0.
The script reports a fixed firmware counter set including PCC_CNP_COUNT, MAD_RTT_PERF_CONT_REQ/RES, the WRED-drop families for SX, ACK, NACK, CNP, and RTT events, HANDLED_SXW/RXT_EVENTS, and per-port DROP_RTT and RTT_GEN counters. The set is not user-extensible.
The mst device path you passed does not match any entry in sudo mst status -v. Run sudo mst start, then sudo mst status -v, and use the exact device path it lists for your NIC.
A zero usually means the device genuinely saw no such events, not a tool bug. Confirm set was run before query and that relevant RoCE traffic is generating congestion, RTT, or drop events before treating a zero as a finding.
No. The script only arms and reads firmware diagnostic counters; it does not change congestion-control behavior or forwarding. Custom PCC algorithm development belongs to the doca-pcc library skill, and firmware PCC configuration is routed through the DOCA documentation.
PlaneInABottleStandardize React Native testing patterns for MST, RTL, and Maestro workflows.
nthpaulControl local browser or CDP-driven UIs to capture before/after evidence artifacts.
hollis-labsRefresh Project Context Cache files with minimal diffs from git changes or explicit scope values.
virtualrusselMonitor RED metrics and runtime telemetry across multiple runtimes using DQL templates.
