DOCA Flow DPA Provider
Where to start: This skill assumes DOCA is already
installed, the user has a BlueField with a DPA processor that
the host can see through DOCA, the user already programs DOCA
Flow from the host (doca-flow) and already runs DPA kernels
from the host (doca-dpa / DPACC compiler), and the user is
doing hands-on DPA Flow Provider work — i.e. using
doca-flow-dpa-provider to export an existing DOCA Flow pipe
or external resource into the DPA address space so a DPA
kernel can manipulate it inline. 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 the provider express on this version + this
BlueField generation. If the user has not installed DOCA yet,
route to doca-setup first; if
the user has not stood up a host-side Flow pipe yet, route to
doca-flow first; if the user has
not stood up host-side DPA execution yet, route to
doca-dpa first.
Example questions this skill answers well
The CLASSES of DPA Flow Provider 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.
- "Is this library even the right tool for what I want?" —
worked example: "I want my DOCA Flow pipe to be readable
from a DPA kernel, OR I want to do something fancier than
the host-side
doca-flow API exposes". Answered by the
decision rule in
CAPABILITIES.md ## Capabilities and modes
("three-program model: when this library is the right
surface vs pure host-side Flow vs pure DPA"). Most
first-time askers do NOT need this library; the skill's
first job is to confirm they do.
- "How do I export an existing DOCA Flow pipe to the DPA
side?" — worked example: "I have a Flow pipe with a
counter on every entry; I want a DPA kernel to read those
counters inline and decide what to do next". Answered by
the host-side export sequence in
CAPABILITIES.md ## Capabilities and modes
- the bring-up steps in
TASKS.md ## configure.
- "How do I drive the exported pipe from inside the DPA
kernel?" — worked example: "I have the device address of
an exported hash pipe; how do I disable an entry from the
DPA, and how do I know the operation completed?".
Answered by the device-side API surface in
CAPABILITIES.md ## Capabilities and modes
("DPA-side consumption") + the host-side queue allocation
- DPA-side polling step in
TASKS.md ## run.
- "What does this
DOCA_ERROR_* from a
doca_flow_dpa_* call mean, and is the bug on the host
side, on the DPA side, or in the export handshake between
them?" — worked example: "DOCA_ERROR_BAD_STATE from
doca_flow_dpa_pipe_export". Answered by the provider
overlay on the cross-library taxonomy in
CAPABILITIES.md ## Error taxonomy
- the layered ladder in
TASKS.md ## debug that escalates to
doca-debug.
- "Why did my pipe export succeed but my DPA kernel never
sees entries?" — worked example: "I called
doca_flow_dpa_pipe_export_prepare AFTER adding entries to
the pipe". Answered by the lifecycle ordering rule in
CAPABILITIES.md ## Safety policy
- the staged-export workflow in
TASKS.md ## test.
- "Is the host-side / DPA-side provider API I'm reading
about on my installed DOCA?" — worked example: "is the
three-queue-type
doca_flow_dpa_queues_create available
against the DOCA + DPACC versions on this host, or am I
still on the older doca_flow_dpa_pipe_queues-based
surface?". Answered by the version-compatibility overlay
in
CAPABILITIES.md ## Version compatibility
which cross-links the canonical detection chain in
doca-version and adds the
provider-specific overlay inherited from
doca-dpa.
Audience
This skill serves external developers building applications
that consume the DOCA Flow DPA Provider library — i.e.,
users who already have a host-side doca-flow pipe and a
host-side doca-dpa execution context, and who want to wire
the two together so a DPA kernel can read counters from / mutate
entries of / read or write external resources tied to that
Flow pipe inline, instead of round-tripping through the host
CPU. It is not for NVIDIA developers contributing to the
provider library itself, nor is it for users who only need
host-side Flow programming (that is doca-flow) or who only
need generic DPA compute that has nothing to do with Flow
(that is doca-dpa).
Language scope. DOCA Flow DPA Provider ships as a paired
library: a host-side C library (pkg-config module
doca-flow-dpa-provider, header
doca_flow_dpa_provider.h) plus a DPA-side device library
that the DPACC compiler links into the DPA-side translation
unit when the kernel includes doca_flow_dpa_provider_dev.h.
Both halves are C. The shipped samples (under the installed
DOCA samples tree) include both translation units. Other-
language host-side consumers can FFI the host C library, but
the DPA-side kernel has no FFI escape hatch (the DPACC
compiler accepts a single translation unit per kernel image).
The skill keeps the lifecycle, capability-discovery, env-
precondition, and error-taxonomy guidance language-neutral on
the host side, and points all DPA-side kernel-writing
questions at the public DOCA DPA and DOCA Flow programming
guides via
doca-public-knowledge-map.
When to load this skill
Load this skill when the user is doing hands-on DOCA Flow DPA
Provider work, in any host language plus a DPA-side
translation unit built by dpacc. Concretely:
- Initializing a
doca_flow_dpa_ctx against a flexio_process
that maps to a BlueField with a DPA processor visible to
the host AND a host-side doca-flow port already brought
up against the same device.
- Allocating the three DPA-side queue types (general /
entries, resources-write, resources-read) for a port via
doca_flow_dpa_queues_create.
- Exporting a host-side
doca_flow_pipe to the DPA address
space via the
doca_flow_dpa_pipe_export_prepare → _pipe_export →
_pipe_get_device_addr sequence, BEFORE any entry is added
to the pipe.
- Exporting an external Flow resource (index-selector
resource, memory resource) to the DPA via the matching
doca_flow_dpa_external_resource_* family.
- Handing the resulting
doca_flow_dpa_addr device pointer to
the DPA-side kernel so the kernel can call
doca_flow_pipe_hash_* / doca_flow_external_resource_*
/ doca_flow_queue_poll_completion on it.
- Debugging a
DOCA_ERROR_* from a doca_flow_dpa_* call —
in particular disambiguating export called too late in the
pipe lifecycle from queues not yet created from DPA-
side queue full and not drained.
- Designing host-side bindings in a non-C language that drive
the provider's host-side setup and hand the device address
off to a DPA application image built separately with
dpacc.
Do not load this skill for general DOCA Flow programming
(use doca-flow), generic host-side
DPA work (use doca-dpa), or DPA-
side kernel-writing itself (route via
doca-public-knowledge-map
to the public DOCA DPA / DPACC / Flow programming guides).
What this skill provides
This is a thin loader. The body keeps only the orientation
needed to pick the right next file. The substantive
provider-specific material lives in two companion files:
CAPABILITIES.md — what the host-side and DPA-side provider
API can express on this version + this BlueField
generation: the per-port doca_flow_dpa_ctx context, the
three queue types (DOCA_FLOW_DPA_QUEUE_TYPE_GENERAL /
_RESOURCES_WRITE / _RESOURCES_READ), the
pipe-export handshake (prepare → export → get-device-addr),
the parallel external-resource-export handshake, the DPA-
side device API for hash-pipe entry manipulation
(doca_flow_pipe_hash_enable_index /
_hash_disable_index / _hash_replace_index), the DPA-
side device API for external resources
(doca_flow_external_resource_index_selector_modify*,
doca_flow_external_resource_memory_update,
doca_flow_external_resource_memory_read*), the
completion-queue polling
(doca_flow_queue_poll_completion), the
three-program-model rule (host-side doca-flow + host-side
doca-dpa + DPA-side kernel), the error taxonomy mapped
onto the cross-library DOCA_ERROR_* set, the
observability surface, and the safety policy that gates the
export lifecycle.
TASKS.md — step-by-step workflows for the in-scope
provider verbs: install, configure, build, modify,
run, test, debug, use. Plus a Deferred task verbs
block that points out-of-scope questions at the right next
skill.
The skill assumes a host where DOCA is already installed at
the standard location, a BlueField with a DPA processor is
physically present and visible to the host, the DPACC
compiler is installed at a version matched to the DOCA
install per the DOCA Compatibility Policy, the user already
knows how to bring up a doca-flow port and create a
host-side doca_dpa (or its FlexIO equivalent) for kernel
execution, and the user has at least a sketch of the DPA-side
kernel that will consume the exported pipe device address.
What this skill deliberately does not ship
This skill is agent guidance, not a samples or templates
bundle. To keep the boundary clean, it deliberately does not
contain — and pull requests should not add:
- Pre-written DOCA Flow DPA Provider application source
code or DPA-side kernel source, in any language. The
verified provider source is the shipped C + DPA-side
samples under the installed DOCA samples tree (route via
doca-public-knowledge-map
for the per-install sample tree path). The agent's job is
to route the user to those files and prescribe a
minimum-diff modification on them via the universal
modify-a-sample workflow in
doca-programming-guide,
layered with the provider-specific overrides in
TASKS.md ## modify.
- Standalone build manifests (
meson.build,
CMakeLists.txt, …) parked inside the skill. The agent
constructs the build manifest in the user's project
directory against the user's installed DOCA + DPACC
compiler, where pkg-config --modversion doca-flow-dpa-provider (alongside doca-flow and
doca-dpa) and the installed dpacc are the joint sources
of truth.
- A
samples/, bindings/, or reference/ subtree of
any kind. A mock or incomplete artifact in this skill's
tree, even one labeled "reference", is misleading: users
will read it as buildable.
- Host-side
doca-flow pipe-spec content. That is
doca-flow's scope; this skill
exports an already-constructed pipe and does not redefine
how to construct it.
- DPA-side kernel programming generalities. Writing the
DPA-side function body, allocating DPA memory inside the
kernel, intrinsics, DPA-side libraries like
doca-dpa-comms and doca-dpa-verbs — out of scope. Route
to the public DOCA DPA / DPACC guides via
doca-public-knowledge-map.
Loading order
- Read this
SKILL.md first to confirm the user's question
is in scope (Flow-pipe-exported-to-DPA work, not pure
doca-flow work and not generic doca-dpa work).
- For the provider capability matrix, the three-program
model, the per-port
doca_flow_dpa_ctx, the three queue
types, the pipe-export and external-resource-export
handshakes, the DPA-side device API surface, the
completion model, the error taxonomy, the observability
surface, and the safety policy, see
CAPABILITIES.md.
- For step-by-step workflows — install, configure, build,
modify, run, test, debug, use — see
TASKS.md.
Both companion files cross-link to each other,
doca-flow and
doca-dpa for the host-side
surfaces this library bridges,
doca-version for the
canonical DOCA version-handling rules (with the
DOCA-and-DPACC overlay inherited from
doca-dpa), and
doca-public-knowledge-map
whenever the right answer is "look it up in the public DOCA
Flow / DOCA DPA / DPACC programming guides, or in the on-disk
install layout" rather than "provider-specific guidance".
Related skills
doca-flow — the canonical
host-side Flow programming skill. The Flow pipe this
library exports MUST be brought up against
doca-flow CAPABILITIES.md ## Capabilities and modes
first; this skill only adds the DPA-export layer on top.
doca-dpa — the host-side DPA
control library. The DPA kernel that consumes the
exported device address is loaded and launched through
doca-dpa (or its FlexIO-process equivalent); this skill
inherits the two-side-program model, the DPACC-and-DOCA
version-match rule, and the env-precondition matrix from
there.
doca-public-knowledge-map —
routing table for every public DOCA documentation source
(DOCA Flow guide at
https://docs.nvidia.com/doca/sdk/doca-flow/index.html;
DOCA DPA guide at
https://docs.nvidia.com/doca/sdk/doca-dpa/index.html;
DPACC compiler guide and DPA Tools umbrella reachable from
the same routing table) and the on-disk layout of an
installed DOCA package.
doca-setup — env preparation,
install verification, DPACC compiler install /
verification, and the I have no install yet path with
the public NGC DOCA container. This skill assumes its
preconditions are satisfied AND that DPACC is installed at
a version that matches DOCA.
doca-version — canonical
DOCA version-handling rules. This skill's ## Version compatibility cross-links the four-way match rule and adds
the provider-specific DOCA-and-DPACC must match overlay
per the DOCA Compatibility Policy (inherited from
doca-dpa).
doca-structured-tools-contract —
the bundle's structured-tools precedence rule (detect /
prefer / fall back / report). The Command appendix in
TASKS.md honors this contract.
doca-programming-guide —
general DOCA programming patterns: the canonical
pkg-config + meson build pattern, the universal
modify-a-shipped-sample first-app workflow, the universal
Core-context lifecycle, the cross-library DOCA_ERROR_*
taxonomy, and the program-side debug order. This skill
layers provider specifics on top.
doca-debug — the cross-cutting
debug ladder (install / version / build / link / runtime /
program / driver). Provider-specific debug (lifecycle-
ordering between Flow pipe creation, queue creation, export
prepare, entry add, export; queue-full on DPA-side polling;
pipe device address handed to a kernel that targets a
different doca_flow_dpa_ctx) overlays on top.
doca-hardware-safety —
cross-cutting hardware-safety meta-policy that this
skill's ## Safety policy overlays. Because the exported
pipe is mutated inline by DPA-side kernel code, the
validate-before-commit discipline from doca-flow plus the
two-side-program rebuild discipline from doca-dpa BOTH
apply, and the meta-policy provides the cross-cutting
framing.
1---2license: Apache-2.03name: doca-flow-dpa-provider4description: >5 Use this skill when the user is doing hands-on DOCA Flow DPA6 Provider work — exporting a `doca-flow` pipe or external7 resource (index-selector/memory) into BlueField DPA8 address space so a DPACC-built kernel can read counters, mutate9 hash-pipe entries, and update/read memory or index-selector10 resources inline with Flow. Covers per-port11 `doca_flow_dpa_ctx`, three queue types12 (general/resources-write/resources-read), the order-sensitive13 export handshake (`_export_prepare` → add entries → `_export` →14 `_get_device_addr`), and DPA-side device API. Trigger even15 when the user does not say "DOCA Flow DPA Provider" — implicit16 phrasings include "DPA kernel never sees entries in the exported17 pipe", "BAD_STATE from `_pipe_export`", "how do I disable a hash18 entry from a DPA kernel", "DPA memory read returns no value", or19 "DPA-side post keeps returning AGAIN". Refuse and route20 elsewhere for `doca-flow` pipe construction, generic21 host-side DPA (`doca-dpa`), or DPA-side kernel-writing — those22 belong to other skills.23metadata:24 source: https://skillmd.com/skills/nvidia/doca-flow-dpa-provider25 kind: library26compatibility: >27 Requires DOCA SDK installed at /opt/mellanox/doca on Linux28 (Ubuntu 22.04/24.04 or RHEL/SLES) with a BlueField DPU exposing29 a DPA processor visible to the host, PLUS the DPACC compiler30 installed at a version matched to DOCA per the DOCA Compatibility31 Policy. Reads the user's local install via `pkg-config32 doca-flow-dpa-provider` (cross-checked with `doca-flow`,33 `doca-dpa`, and installed `dpacc`). ConnectX-only hosts cannot34 use this library.35---3637# DOCA Flow DPA Provider3839**Where to start:** This skill assumes DOCA is already40installed, the user has a BlueField with a DPA processor that41the host can see through DOCA, the user already programs DOCA42Flow from the host (`doca-flow`) and already runs DPA kernels43from the host (`doca-dpa` / DPACC compiler), and the user is44doing **hands-on DPA Flow Provider work** — i.e. using45`doca-flow-dpa-provider` to export an existing DOCA Flow pipe46or external resource into the DPA address space so a DPA47kernel can manipulate it inline. Open [`TASKS.md`](TASKS.md)48if the user wants to *do* something (configure / build /49modify / run / test / debug); open50[`CAPABILITIES.md`](CAPABILITIES.md) when the question is51*what can the provider express* on this version + this52BlueField generation. If the user has not installed DOCA yet,53route to [`doca-setup`](../../doca-setup/SKILL.md) first; if54the user has not stood up a host-side Flow pipe yet, route to55[`doca-flow`](../doca-flow/SKILL.md) first; if the user has56not stood up host-side DPA execution yet, route to57[`doca-dpa`](../doca-dpa/SKILL.md) first.5859## Example questions this skill answers well6061The CLASSES of DPA Flow Provider questions this skill is built62to answer, each with one worked example. The agent should63treat the *class* as the load-bearing piece — the worked64example is a single instance.6566- **"Is this library even the right tool for what I want?"** —67 worked example: *"I want my DOCA Flow pipe to be readable68 from a DPA kernel, OR I want to do something fancier than69 the host-side `doca-flow` API exposes"*. Answered by the70 decision rule in71 [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes)72 ("three-program model: when this library is the right73 surface vs pure host-side Flow vs pure DPA"). Most74 first-time askers do NOT need this library; the skill's75 first job is to confirm they do.76- **"How do I export an existing DOCA Flow pipe to the DPA77 side?"** — worked example: *"I have a Flow pipe with a78 counter on every entry; I want a DPA kernel to read those79 counters inline and decide what to do next"*. Answered by80 the host-side export sequence in81 [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes)82 + the bring-up steps in83 [`TASKS.md ## configure`](TASKS.md#configure).84- **"How do I drive the exported pipe from inside the DPA85 kernel?"** — worked example: *"I have the device address of86 an exported hash pipe; how do I disable an entry from the87 DPA, and how do I know the operation completed?"*.88 Answered by the device-side API surface in89 [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes)90 ("DPA-side consumption") + the host-side queue allocation91 + DPA-side polling step in92 [`TASKS.md ## run`](TASKS.md#run).93- **"What does this `DOCA_ERROR_*` from a94 `doca_flow_dpa_*` call mean, and is the bug on the host95 side, on the DPA side, or in the export handshake between96 them?"** — worked example: *"`DOCA_ERROR_BAD_STATE` from97 `doca_flow_dpa_pipe_export`"*. Answered by the provider98 overlay on the cross-library taxonomy in99 [`CAPABILITIES.md ## Error taxonomy`](CAPABILITIES.md#error-taxonomy)100 + the layered ladder in101 [`TASKS.md ## debug`](TASKS.md#debug) that escalates to102 [`doca-debug`](../../doca-debug/SKILL.md).103- **"Why did my pipe export *succeed* but my DPA kernel never104 sees entries?"** — worked example: *"I called105 `doca_flow_dpa_pipe_export_prepare` AFTER adding entries to106 the pipe"*. Answered by the lifecycle ordering rule in107 [`CAPABILITIES.md ## Safety policy`](CAPABILITIES.md#safety-policy)108 + the staged-export workflow in109 [`TASKS.md ## test`](TASKS.md#test).110- **"Is the host-side / DPA-side provider API I'm reading111 about on my installed DOCA?"** — worked example: *"is the112 three-queue-type `doca_flow_dpa_queues_create` available113 against the DOCA + DPACC versions on this host, or am I114 still on the older `doca_flow_dpa_pipe_queues`-based115 surface?"*. Answered by the version-compatibility overlay116 in117 [`CAPABILITIES.md ## Version compatibility`](CAPABILITIES.md#version-compatibility)118 which cross-links the canonical detection chain in119 [`doca-version`](../../doca-version/SKILL.md) and adds the120 provider-specific overlay inherited from121 [`doca-dpa`](../doca-dpa/SKILL.md).122123## Audience124125This skill serves **external developers building applications126that consume the DOCA Flow DPA Provider library** — i.e.,127users who already have a host-side `doca-flow` pipe and a128host-side `doca-dpa` execution context, and who want to wire129the two together so a DPA kernel can read counters from / mutate130entries of / read or write external resources tied to that131Flow pipe inline, instead of round-tripping through the host132CPU. It is *not* for NVIDIA developers contributing to the133provider library itself, nor is it for users who only need134host-side Flow programming (that is `doca-flow`) or who only135need generic DPA compute that has nothing to do with Flow136(that is `doca-dpa`).137138**Language scope.** DOCA Flow DPA Provider ships as a *paired*139library: a host-side C library (pkg-config module140`doca-flow-dpa-provider`, header141`doca_flow_dpa_provider.h`) plus a DPA-side device library142that the DPACC compiler links into the DPA-side translation143unit when the kernel includes `doca_flow_dpa_provider_dev.h`.144Both halves are C. The shipped samples (under the installed145DOCA samples tree) include both translation units. Other-146language host-side consumers can FFI the host C library, but147the DPA-side kernel has no FFI escape hatch (the DPACC148compiler accepts a single translation unit per kernel image).149The skill keeps the lifecycle, capability-discovery, env-150precondition, and error-taxonomy guidance language-neutral on151the host side, and points all DPA-side kernel-writing152questions at the public DOCA DPA and DOCA Flow programming153guides via154[`doca-public-knowledge-map`](../../doca-public-knowledge-map/SKILL.md).155156## When to load this skill157158Load this skill when the user is doing hands-on DOCA Flow DPA159Provider work, in any host language plus a DPA-side160translation unit built by `dpacc`. Concretely:161162- Initializing a `doca_flow_dpa_ctx` against a `flexio_process`163 that maps to a BlueField with a DPA processor visible to164 the host AND a host-side `doca-flow` port already brought165 up against the same device.166- Allocating the three DPA-side queue types (general /167 entries, resources-write, resources-read) for a port via168 `doca_flow_dpa_queues_create`.169- Exporting a host-side `doca_flow_pipe` to the DPA address170 space via the171 `doca_flow_dpa_pipe_export_prepare` → `_pipe_export` →172 `_pipe_get_device_addr` sequence, BEFORE any entry is added173 to the pipe.174- Exporting an external Flow resource (index-selector175 resource, memory resource) to the DPA via the matching176 `doca_flow_dpa_external_resource_*` family.177- Handing the resulting `doca_flow_dpa_addr` device pointer to178 the DPA-side kernel so the kernel can call179 `doca_flow_pipe_hash_*` / `doca_flow_external_resource_*`180 / `doca_flow_queue_poll_completion` on it.181- Debugging a `DOCA_ERROR_*` from a `doca_flow_dpa_*` call —182 in particular disambiguating *export called too late in the183 pipe lifecycle* from *queues not yet created* from *DPA-184 side queue full and not drained*.185- Designing host-side bindings in a non-C language that drive186 the provider's host-side setup and hand the device address187 off to a DPA application image built separately with188 `dpacc`.189190Do **not** load this skill for general DOCA Flow programming191(use [`doca-flow`](../doca-flow/SKILL.md)), generic host-side192DPA work (use [`doca-dpa`](../doca-dpa/SKILL.md)), or DPA-193side kernel-writing itself (route via194[`doca-public-knowledge-map`](../../doca-public-knowledge-map/SKILL.md)195to the public DOCA DPA / DPACC / Flow programming guides).196197## What this skill provides198199This is a **thin loader**. The body keeps only the orientation200needed to pick the right next file. The substantive201provider-specific material lives in two companion files:202203- `CAPABILITIES.md` — what the host-side and DPA-side provider204 API can express on this version + this BlueField205 generation: the per-port `doca_flow_dpa_ctx` context, the206 three queue types (`DOCA_FLOW_DPA_QUEUE_TYPE_GENERAL` /207 `_RESOURCES_WRITE` / `_RESOURCES_READ`), the208 pipe-export handshake (prepare → export → get-device-addr),209 the parallel external-resource-export handshake, the DPA-210 side device API for hash-pipe entry manipulation211 (`doca_flow_pipe_hash_enable_index` /212 `_hash_disable_index` / `_hash_replace_index`), the DPA-213 side device API for external resources214 (`doca_flow_external_resource_index_selector_modify*`,215 `doca_flow_external_resource_memory_update`,216 `doca_flow_external_resource_memory_read*`), the217 completion-queue polling218 (`doca_flow_queue_poll_completion`), the219 three-program-model rule (host-side `doca-flow` + host-side220 `doca-dpa` + DPA-side kernel), the error taxonomy mapped221 onto the cross-library `DOCA_ERROR_*` set, the222 observability surface, and the safety policy that gates the223 export lifecycle.224- `TASKS.md` — step-by-step workflows for the in-scope225 provider verbs: `install`, `configure`, `build`, `modify`,226 `run`, `test`, `debug`, `use`. Plus a `Deferred task verbs`227 block that points out-of-scope questions at the right next228 skill.229230The skill assumes a host where DOCA is already installed at231the standard location, a BlueField with a DPA processor is232physically present and visible to the host, the DPACC233compiler is installed at a version matched to the DOCA234install per the DOCA Compatibility Policy, the user already235knows how to bring up a `doca-flow` port and create a236host-side `doca_dpa` (or its FlexIO equivalent) for kernel237execution, and the user has at least a sketch of the DPA-side238kernel that will consume the exported pipe device address.239240## What this skill deliberately does not ship241242This skill is **agent guidance**, not a samples or templates243bundle. To keep the boundary clean, it deliberately does not244contain — and pull requests should not add:245246- **Pre-written DOCA Flow DPA Provider application source247 code or DPA-side kernel source, in any language.** The248 verified provider source is the shipped C + DPA-side249 samples under the installed DOCA samples tree (route via250 [`doca-public-knowledge-map`](../../doca-public-knowledge-map/SKILL.md)251 for the per-install sample tree path). The agent's job is252 to route the user to those files and prescribe a253 minimum-diff modification on them via the universal254 modify-a-sample workflow in255 [`doca-programming-guide`](../../doca-programming-guide/SKILL.md),256 layered with the provider-specific overrides in257 [`TASKS.md ## modify`](TASKS.md#modify).258- **Standalone build manifests** (`meson.build`,259 `CMakeLists.txt`, …) parked inside the skill. The agent260 constructs the build manifest *in the user's project261 directory* against the user's installed DOCA + DPACC262 compiler, where `pkg-config --modversion263 doca-flow-dpa-provider` (alongside `doca-flow` and264 `doca-dpa`) and the installed `dpacc` are the joint sources265 of truth.266- **A `samples/`, `bindings/`, or `reference/` subtree** of267 any kind. A mock or incomplete artifact in this skill's268 tree, even one labeled "reference", is misleading: users269 will read it as buildable.270- **Host-side `doca-flow` pipe-spec content.** That is271 [`doca-flow`](../doca-flow/SKILL.md)'s scope; this skill272 *exports* an already-constructed pipe and does not redefine273 how to construct it.274- **DPA-side kernel programming generalities.** Writing the275 DPA-side function body, allocating DPA memory inside the276 kernel, intrinsics, DPA-side libraries like277 `doca-dpa-comms` and `doca-dpa-verbs` — out of scope. Route278 to the public DOCA DPA / DPACC guides via279 [`doca-public-knowledge-map`](../../doca-public-knowledge-map/SKILL.md).280281## Loading order2822831. Read this `SKILL.md` first to confirm the user's question284 is in scope (Flow-pipe-exported-to-DPA work, not pure285 `doca-flow` work and not generic `doca-dpa` work).2862. **For the provider capability matrix, the three-program287 model, the per-port `doca_flow_dpa_ctx`, the three queue288 types, the pipe-export and external-resource-export289 handshakes, the DPA-side device API surface, the290 completion model, the error taxonomy, the observability291 surface, and the safety policy, see292 [CAPABILITIES.md](CAPABILITIES.md).**2933. **For step-by-step workflows — install, configure, build,294 modify, run, test, debug, use — see295 [TASKS.md](TASKS.md).**296297Both companion files cross-link to each other,298[`doca-flow`](../doca-flow/SKILL.md) and299[`doca-dpa`](../doca-dpa/SKILL.md) for the host-side300surfaces this library bridges,301[`doca-version`](../../doca-version/SKILL.md) for the302canonical DOCA version-handling rules (with the303DOCA-and-DPACC overlay inherited from304[`doca-dpa`](../doca-dpa/SKILL.md)), and305[`doca-public-knowledge-map`](../../doca-public-knowledge-map/SKILL.md)306whenever the right answer is "look it up in the public DOCA307Flow / DOCA DPA / DPACC programming guides, or in the on-disk308install layout" rather than "provider-specific guidance".309310## Related skills311312- [`doca-flow`](../doca-flow/SKILL.md) — the canonical313 host-side Flow programming skill. The Flow pipe this314 library exports MUST be brought up against315 [`doca-flow CAPABILITIES.md ## Capabilities and modes`](../doca-flow/CAPABILITIES.md#capabilities-and-modes)316 first; this skill only adds the DPA-export layer on top.317- [`doca-dpa`](../doca-dpa/SKILL.md) — the host-side DPA318 control library. The DPA kernel that consumes the319 exported device address is loaded and launched through320 `doca-dpa` (or its FlexIO-process equivalent); this skill321 inherits the two-side-program model, the DPACC-and-DOCA322 version-match rule, and the env-precondition matrix from323 there.324- [`doca-public-knowledge-map`](../../doca-public-knowledge-map/SKILL.md) —325 routing table for every public DOCA documentation source326 (DOCA Flow guide at327 <https://docs.nvidia.com/doca/sdk/doca-flow/index.html>;328 DOCA DPA guide at329 <https://docs.nvidia.com/doca/sdk/doca-dpa/index.html>;330 DPACC compiler guide and DPA Tools umbrella reachable from331 the same routing table) and the on-disk layout of an332 installed DOCA package.333- [`doca-setup`](../../doca-setup/SKILL.md) — env preparation,334 install verification, DPACC compiler install /335 verification, and the *I have no install yet* path with336 the public NGC DOCA container. This skill assumes its337 preconditions are satisfied AND that DPACC is installed at338 a version that matches DOCA.339- [`doca-version`](../../doca-version/SKILL.md) — canonical340 DOCA version-handling rules. This skill's `## Version341 compatibility` cross-links the four-way match rule and adds342 the provider-specific *DOCA-and-DPACC must match* overlay343 per the DOCA Compatibility Policy (inherited from344 [`doca-dpa`](../doca-dpa/SKILL.md)).345- [`doca-structured-tools-contract`](../../doca-structured-tools-contract/SKILL.md) —346 the bundle's structured-tools precedence rule (detect /347 prefer / fall back / report). The Command appendix in348 [TASKS.md](TASKS.md) honors this contract.349- [`doca-programming-guide`](../../doca-programming-guide/SKILL.md) —350 general DOCA programming patterns: the canonical351 `pkg-config` + meson build pattern, the universal352 modify-a-shipped-sample first-app workflow, the universal353 Core-context lifecycle, the cross-library `DOCA_ERROR_*`354 taxonomy, and the program-side debug order. This skill355 layers provider specifics on top.356- [`doca-debug`](../../doca-debug/SKILL.md) — the cross-cutting357 debug ladder (install / version / build / link / runtime /358 program / driver). Provider-specific debug (lifecycle-359 ordering between Flow pipe creation, queue creation, export360 prepare, entry add, export; queue-full on DPA-side polling;361 pipe device address handed to a kernel that targets a362 different `doca_flow_dpa_ctx`) overlays on top.363- [`doca-hardware-safety`](../../doca-hardware-safety/SKILL.md) —364 cross-cutting hardware-safety meta-policy that this365 skill's `## Safety policy` overlays. Because the exported366 pipe is mutated inline by DPA-side kernel code, the367 validate-before-commit discipline from `doca-flow` plus the368 two-side-program rebuild discipline from `doca-dpa` BOTH369 apply, and the meta-policy provides the cross-cutting370 framing.371