Agent skill · NVIDIA
doca-eth
Use this skill for hands-on DOCA Ethernet packet-queue work on a BlueField DPU or ConnectX NIC — bringing up a `doca_eth_rxq` or `doca_eth_txq` on a port / representor / SF, picking among the four `enum doca_eth_rxq_type` values (`_REGULAR` / `_CYCLIC` / `_MANAGED_MEMPOOL` / `_SHARED_MEMPOOL`), sizing burst or scatter-gather length against the `_cap_*` queries, submitting `doca_eth_txq_task_send` / `_lso_send` (carrying packet `doca_buf`s — no `doca_eth_frame` struct exists), or debugging DOCA_ERROR_* from an Ethernet call. Trigger on implicit phrasings: "my RX queue is up but no packets arrive", "send-task returns AGAIN at line rate", "which queue type for fixed-MTU ingress", "device open fails without sudo", or "is L3 checksum offload available here". Refuse and route elsewhere for installing DOCA, flow-rule / steering programming, host↔DPU control messaging, or RDMA data movement.
What it needs
About 7k tokens when loaded.
What this skill does
DOCA Ethernet Where to start: This skill assumes DOCA is already installed and the user is doing hands-on packet-queue work on a host or BlueField with DOCA. Open TASKS.md if the user wants to do something (configure / build / modify / run / test / debug); open CAPABILITIES.md when the question is what can a DOCA Ethernet queue express on this version. If the user has not installed DOCA yet, route to doca-setup first. If the user is asking "how do I get packets to land on my RX queue at all", the answer lives in doca-flow — DOCA Ethernet is the queue surface; DOCA Flow is the steering surface, and they are independent libraries. Example questions this skill answers well The CLASSES of DOCA Ethernet questions this skill is built to answer, each with one worked example. The agent should treat the class as the load-bearing piece — the worked example is a single instance. "How do I bring up an RX and TX queue on a representor or physical port?" — worked example: "set up a docaethrxq plus a docaethtxq on a single BlueField representor for first-run testing". Answered by the queue-pair lifecycle in TASKS.md ## configure + CAPABILITIES.md ## Capabilities and modes RX / TX object table. "Which RX type fits my data shape — regular, cyclic, or managed-recv?" — worked example: "line-rate ingress with fixed-size frames into a pre-allocated buffer ring". Answered by the RX-type taxonomy in CAPABILITIES.md ## Capabilities and modes the capability-query rule (docaethrxqcapistypesupported against a docadevinfo) in TASKS.md ## configure. "How do I send a packet from user code through docaethtxq?" — worked example: "allocate a packet docabuf, attach the payload, submit one send-task, wait for the completion event". Answered by the TX submission shape in CAPABILITIES.md ## Capabilities and modes the property-set workflow in TASKS.md ## modify. "My queue is up but no packets arrive — why?" — worked example: "docaethrxq started cleanly but the recv callback never fires". …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/doca-eth