What problem does it solve?
Developers with existing DPDK packet-processing applications often need DOCA capabilities like hardware steering without rewriting their data-plane. This Skill guides agents through binding DPDK port IDs to DOCA devices, converting mbufs to DOCA buffers, and diagnosing bridge errors across the DPDK-DOCA version boundary.
Core Features & Use Cases
- Port Handover Guidance: Walks through binding a DPDK port id to a
doca_dev using doca_dpdk_port_probe and doca_dpdk_port_as_dev so DOCA Flow can program steering rules on the same physical port.
- Version Compatibility Checks: Enforces the matched-pair DPDK-DOCA version coupling via pkg-config probes before any code change, preventing the common "bridge loads but every operation fails" failure mode.
- Error Diagnosis: Maps bridge-specific
DOCA_ERROR_* returns (BAD_STATE, NOT_FOUND, NOT_PERMITTED) to root causes across lifecycle, permission, and version layers.
- Use Case: A network engineer has a production DPDK app and wants to add DOCA Flow hardware steering rules on its ports; the Skill walks configure, build, run, test, and debug steps without a data-plane rewrite.
Quick Start
Ask your agent: "How do I add DOCA Flow steering rules to my existing DPDK application without rewriting the data plane?"