What problem does it solve?
Developers building applications that exchange control or data messages between a host process and a BlueField DPU over PCIe face tricky decisions: server vs client role assignment, slow-path vs fast-path selection, capability discovery, and cryptic DOCA_ERROR_* failures. This Skill provides structured guidance for the entire DOCA Comch workflow so agents give correct, version-aware answers instead of generic networking advice.
Core Features & Use Cases
- Role and path selection: Establishes the asymmetric model (server on DPU, client on host) and chooses between slow-path send-task/recv-callback and fast-path producer/consumer based on throughput needs.
- Capability discovery and error diagnosis: Queries doca_comch_cap_get_* for max message size and client limits, and maps DOCA_ERROR_* returns (BAD_STATE, AGAIN, NOT_PERMITTED, CONNECTION_RESET) to root causes.
- Version compatibility handling: Covers the DOCA 2.5 rename from Comm Channel to Comch and detects partial installs via pkg-config checks.
- Use Case: A developer sees DOCA_ERROR_NOT_PERMITTED from doca_comch_server_create on a freshly imaged BlueField; the Skill walks the representor visibility and permission matrix to fix the environment before touching code.
Quick Start
Ask your agent to help you bring up a Comch channel between the host and BlueField DPU, choosing server and client roles and sending a first control message.