domains / families / devops / doca-rdmi

doca-rdmi

separate

Use this skill when the user works with DOCA RDMI, the RDMA Initiator library that lets a DPA-resident function originate one-sided RDMA toward a remote responder. Covers choosing doca-rdmi versus doca-rdma, instantiating doca_rdmi_connection and doca_rdmi_poster, wiring doca_dpa_completion or doca_verbs_cq ahead of doca_ctx_start(), exporting the datapath handle consumed on-DPA, auditing whether a doca_rdmi_* symbol is EXPERIMENTAL for the installed release, or decoding DOCA_ERROR_* statuses such as BAD_STATE at completion-attach. Also load it for implied asks like "my Arm-side function must originate RDMA writes", "symbol missing at link time on doca_rdmi_*", or "posted work request never arrived". Refuse and route to the proper owner for two-sided host RDMA, GPU-originated traffic, or generic IB/RoCE theory.

When to use

• Choosing doca-rdmi versus doca-rdma
• Instantiating doca_rdmi_connection and doca_rdmi_poster
• Wiring doca_dpa_completion or doca_verbs_cq
• Exporting the datapath handle consumed on-DPA
• Auditing whether a doca_rdmi_* symbol is EXPERIMENTAL
• Decoding DOCA_ERROR_* statuses
• Originating RDMA writes from an Arm-side function
• Debugging missing symbols or unarrived work requests

When not to use

• Two-sided host RDMA
• GPU-originated traffic
• Generic IB/RoCE theory

Skill page

Source