What problem does it solve?
Developers building DPA-resident DOCA applications struggle to correctly use the DOCA RDMI (RDMA Initiator) library: choosing between doca-rdmi and doca-rdma, ordering connection/poster lifecycle calls around doca_ctx_start(), attaching the right completion source, and interpreting EXPERIMENTAL symbols and DOCA_ERROR_* returns. This Skill provides verified, version-aware guidance for those workflows.
Core Features & Use Cases
- Surface selection and object lifecycle: Decide doca-rdmi vs doca-rdma vs doca-verbs, then stand up doca_rdmi_connection and doca_rdmi_poster objects with correct configure-start-use-stop-destroy ordering.
- DPA datapath handoff and completions: Attach a doca_dpa_completion or doca_verbs_cq before start, retrieve DPA-side handles, and wire the host-side recv_ack loop.
- Version auditing and debugging: Confirm EXPERIMENTAL doca_rdmi_* symbols against installed headers via pkg-config, and diagnose DOCA_ERROR_* returns with a layered debug ladder and rollback procedure.
- Use Case: A developer whose DPA kernel must post RDMA writes to a remote responder gets a step-by-step walkthrough from install verification through build, run, test, and debug, grounded in the installed DOCA package.
Quick Start
Ask your agent to walk you through setting up a doca_rdmi_connection with a DPA completion so your DPA kernel can post RDMA writes to a remote responder.