What problem does it solve?
Developers building GPU-initiated networking applications with NVIDIA DOCA GPUNetIO face confusing version mismatches, missing GPUDirect RDMA preconditions, and cryptic DOCA_ERROR_* returns. This Skill gives an AI agent the exact workflows to configure, build, run, test, and debug GPUNetIO programs correctly.
Core Features & Use Cases
- GPUNetIO configuration workflows: Step-by-step guidance for creating the per-GPU doca_gpu context, layering doca_gpu_eth_rxq / doca_gpu_eth_txq handles on doca-eth queues, and registering cudaMalloc buffer pools via doca_buf_arr_create_*.
- Dual capability discovery: Enforces checking both the DOCA cap-query (doca_eth_rxq_cap_is_type_supported) and the CUDA side (cudaGetDeviceProperties) before assuming a GPU supports GPUNetIO.
- Persistent-kernel pattern and error taxonomy: Prescribes the long-running CUDA kernel design over kernel-per-packet, and maps DOCA_ERROR_NOT_SUPPORTED, _DRIVER, _AGAIN, _BAD_STATE, and _INVALID_VALUE to root causes.
- Use Case: A developer sees DOCA_ERROR_DRIVER on doca_gpu_create; the agent walks the CUDA/DOCA version-match check, verifies nvidia_peermem is loaded, and isolates the failing layer.
Quick Start
Ask your agent: "Help me write a persistent CUDA kernel that receives packets directly from a DOCA Ethernet queue using GPUNetIO."