What problem does it solve?
Developers building GPU-resident DOCA applications need to wire a GPU-Packet-Initiator context so a CUDA kernel can post RDMA work directly from GPU memory without host CPU mediation, but the doca_gpi object model, lifecycle ordering, and GPU-side handle handoff are easy to get wrong.
Core Features & Use Cases
- Surface Selection Guidance: Decide between the lower-level doca-gpi channel surface and the higher-level doca-gpunetio Send/Receive surface before writing code.
- Lifecycle and Configuration Workflows: Step-by-step verbs (install, configure, build, modify, run, test, debug, use) covering doca_gpi_create, domain and channel attribute sizing, endpoint connection-info exchange, and teardown order.
- Error Diagnosis: A GPI-specific overlay on the DOCA_ERROR_* taxonomy that maps failures like DOCA_ERROR_BAD_STATE or DOCA_ERROR_IN_USE to lifecycle ordering, sizing, or driver-layer causes.
- Use Case: A developer with a BlueField-3 DPU and an NVIDIA GPU asks how to hand a doca_gpu_gpi_channel* handle to a CUDA kernel; the skill walks them through creating the GPI instance, sizing the domain and channel attributes, retrieving the GPU handle, and connecting endpoints to a remote peer.
Quick Start
Ask your agent to help you bring up a DOCA GPI channel and hand the GPU-side handle to your CUDA kernel so it can post RDMA work directly from GPU memory.