DOCA Flow DPA Perf (doca_flow_dpa_perf)
Where to start: This is a tool skill for invoking
doca_flow_dpa_perf, the DPA-accelerated Flow performance tool.
Open TASKS.md and start at
## configure to confirm DPA-capable
hardware + VNF Flow mode + the active / passive device split, then
## run for the smoke-before-bulk flow with a
small operation count before any sweep, then
## test for the eval-loop overlay that gates
defensible Kops/sec numbers. Open CAPABILITIES.md
when the question is what doca_flow_dpa_perf can measure,
what the DPA preconditions are, which devices it runs on,
or how to interpret update / disable / self-test output without
fooling yourself. If DOCA is not installed yet, route to
doca-setup first; if the device is
not DPA-capable (no ConnectX-7+ or BlueField-3+) then this tool is
the wrong surface and the right answer is
doca-flow-perf.
Example questions this skill answers well
The CLASSES of doca_flow_dpa_perf questions this skill is built
to answer, each with one worked example. The class is the
load-bearing piece; the worked example is one instance.
- "Should I measure the DPA-offloaded Flow path or the
host / DPU-CPU Flow path for this question?" — worked
example: "my workload programs path-selector entries via
DOCA Flow; do I baseline with
doca_flow_dpa_perf or with
doca_flow_perf?". Answered by the DPA-vs-host boundary
in
CAPABILITIES.md ## Capabilities and modes
and the device-preconditions table.
- "What does the DPA-offload actually accelerate, and what
doesn't it change?" — worked example: "if I move my Flow
rule update path to the DPA, what changes in the data plane
for the packets themselves?". Answered by the DPA-Provider
scope in
CAPABILITIES.md ## Capabilities and modes.
- "What hardware do I need to use this tool at all?" —
worked example: "is my BlueField-2 DPA-capable?". Answered
by the device-preconditions table in
CAPABILITIES.md ## Capabilities and modes
(BlueField-3 yes, BlueField-2 no; ConnectX-7 minimum
supported, ConnectX-8 recommended, and later generations
supported per the public guide and the
shipped README on the user's install).
- "How do I size my run — burst, queue, completion threshold,
number of operations, iterations — to get a defensible
Kops/sec number?" — worked example: "I want the median
iteration time and standard deviation, not a single noisy
first-iteration spike". Answered by the eval-loop overlay
in
TASKS.md ## test and the iteration-stats
rule in
CAPABILITIES.md ## Observability.
- "My tool reports zero ops / hangs / fails the self-test —
what does that mean?" — worked example: "the tool runs but
the self-test step fails". Answered by the layered error
taxonomy in
CAPABILITIES.md ## Error taxonomy
- the debug ladder in
TASKS.md ## debug.
- "How do I quote a DPA-perf number alongside a host-side
Flow-perf number for the same workload, in a way the next
engineer can actually compare?" — worked example: "two
Kops/sec numbers for what is supposedly the same workload".
Answered by the four-tuple capture rule in
CAPABILITIES.md ## Safety policy
- the per-tool-name rule (the host tool and the DPA tool are
different surfaces; their numbers are not interchangeable
without naming which tool produced which).
Audience
This skill serves external operators, performance engineers,
DOCA Flow application developers, and AI agents who need a
defensible measurement of the DPA-offloaded Flow update path on
DPA-capable hardware. Concretely:
- A platform operator deciding whether to move a path-selector
workload onto the DPA versus keeping it on the host / DPU-CPU
path, and wanting a number to compare.
- A performance engineer producing a "DPA Kops/sec for update
operation, queue-size X, burst-size Y, N workers" baseline
on a specific device + DOCA version so a downstream
comparison is meaningful.
- A DOCA Flow application developer who has already used
doca-dpa to land a DPA-offload of their Flow rule update
path and wants to characterize what the device delivers.
- An AI agent answering "what update rate should I expect from
the DPA-offloaded Flow path on device Y?" honestly — with a
measured number, the command line that produced it, and the
device + DOCA version + as-deployed environment that scopes
it — instead of guessing from datasheet headlines.
It is not for users debugging the tool's source code,
not a substitute for the live public DOCA Flow DPA Perf guide
on docs.nvidia.com, not the place to learn the doca-flow
or doca-dpa APIs (that audience belongs in
doca-flow and
doca-dpa), and not the right
tool for the host / DPU-CPU Flow path (route to
doca-flow-perf).
doca_flow_dpa_perf is shipped as a single CLI binary with
DPA-side device code linked in. The skill uses the same
kind: tool three-file shape as the rest of the bundle so
the agent's task-verb contract is uniform across the bundle.
Language scope
This skill governs invocation, output interpretation, and
recommendation-of-routing for the doca_flow_dpa_perf CLI on
DPA-capable hardware. The tool itself has both a host-side
control (C-language ARGP + DOCA + DPDK code per the shipped
flow_dpa_perf.c / flow_dpa_perf_core.c) and a DPA-side device
component (DPA-side code on the shipped DPA device runtime).
External users do not link any of this; what they configure is
the JSON-config-or-CLI invocation surface. For the
doca-dpa programming model behind the DPA-side execution
engine, see
doca-dpa; for the doca-flow
API behind the pipeline the DPA path executes, see
doca-flow.
When to load this skill
Load this skill when the user is — or the agent needs to —
invoke doca_flow_dpa_perf on a real host with DOCA installed
and a DPA-capable device attached (or the public NGC DOCA
container with the equivalent device passthrough) to measure
update / disable rates on the DPA-offloaded Flow path.
Concretely:
- Confirming DPA preconditions (DPA-capable device class,
VNF Flow mode, recommended PF use, no SFs) before invoking
the tool.
- Picking the active / passive device split appropriate to the
user's hardware (two-port BlueField-3 active + passive; one-
port ConnectX-9 active only).
- Picking the workload-shape axes (burst size, queue size,
completion threshold, hash pipe algorithm, work policy,
number of PSL tables, table size, number of workers).
- Picking the operation axis (update or disable-enable) per the
shipped README's documented operations.
- Producing a defensible Kops/sec number with iteration stats
(median, max, standard deviation) captured.
- Diagnosing zero-ops / hung / failed-self-test runs through
the layered error taxonomy.
Do not load this skill for general DOCA orientation, Flow
program API work, or installation. For those, use
doca-public-knowledge-map,
the matching libs/<library> skill, or
doca-setup. Do not load it for
the host / DPU-CPU Flow path — that audience belongs in
doca-flow-perf.
What this skill provides
This is a thin loader. Substantive material lives in two
companion files:
CAPABILITIES.md — what doca_flow_dpa_perf measures
(the DPA-Provider-on-DPA-device update / disable path
specifically), the DPA-vs-host-path boundary, the
device-preconditions table (ConnectX-7+ / BlueField-3+),
the documented VNF-only Flow-mode rule, the PF-vs-VF-vs-SF
rule (SFs not supported on DPA), the workload-shape axes
(burst, queue, completion threshold, hash pipe algorithm,
work policy, PSL tables, table size, workers), the
operation axis (update vs disable-enable), the version
overlay (this tool rides the doca-flow and doca-dpa
versions it links against; the canonical rules live in
doca-version), the layered
error taxonomy
(config-syntax / device-binding / dpa-precondition /
workload-precondition / measurement-soundness / self-test /
version / cross-cutting), the observability surface
(iteration statistics, self-test path-selector verification,
tcpdump-side traffic verification), and the safety posture
(smoke-before-bulk, four-tuple capture, name the tool that
produced the number).
TASKS.md — step-by-step workflows for the in-scope task
verbs: install (route to setup; the binary is shipped),
configure (DPA-preconditions + active / passive device +
workload-shape decision), build (route to install — the
binary is shipped), modify (refuse — modify the invocation,
not the binary), run (smoke before bulk), test (eval
loop), debug (layered diagnosis), use (consume the
captured number), plus a Deferred task verbs block routing
out-of-scope questions and a Command appendix.
The skill assumes a host where DOCA is already installed (or
the NGC DOCA container is running) on a DPA-capable device and
the operator has the permissions to bind the device and allocate
the DPA execution resources the tool needs.
What this skill deliberately does not ship
This skill is agent guidance, not a samples or scripts
bundle. To keep the boundary clean, it deliberately does not
contain — and pull requests should not add:
- Verbatim default values for flag inventories beyond what
the shipped README or installed
--help documents. Read
defaults from the README first, then fall back to the
installed binary's --help. If neither defines a needed
default, stop and request the operator's explicit value
instead of guessing. The
flag surface is install-specific within the documented
surface; the documented invocations + --help on the
installed version are the authoritative answer. Inventing
a flag is the most common hallucination failure.
- Pre-baked example Kops/sec numbers or expected throughput
numbers. Output is device-, firmware-, DOCA-version-,
workload-, and platform-specific; a pinned number for one
platform misleads operators on a different platform /
version. The shipped README's example numbers are
illustrative, not a baseline the agent should quote as
ground truth.
- Wrappers, parsers, or scripts in any language that
consume the tool's stdout / CSV. The output format is
documented; if a user wants to script against it, the
right answer is "read the live guide, write the parser
against your installed version".
- A
samples/ or reference/ subtree. This is a thin
loader for a documented CLI; substantive material lives on
the public page, in --help, and in the shipped README on
the user's install.
Loading order
- Read this
SKILL.md first to confirm the user's question
is in scope (the user actually wants to invoke
doca_flow_dpa_perf on DPA-capable hardware, not measure
the host / DPU-CPU Flow path).
- For what
doca_flow_dpa_perf measures, the DPA-vs-host
boundary, the device-preconditions table, the workload-
shape axes, the version overlay, the error taxonomy, the
observability surface, and the safety posture, see
CAPABILITIES.md.
- For the documented invocations and the smoke-before-bulk
workflow —
install, configure, build, modify,
run, test, debug, use — see TASKS.md.
Related skills
doca-flow — the base
library whose pipeline this tool measures on the DPA
path. The pipe / entry / rule surface this tool drives is
created by doca-flow program code; the library's pipe
attributes and capability surface are the upstream context.
doca-dpa — the
programming model behind the DPA execution engine the tool
runs on. When the user's question goes from "measure the
DPA path" to "why is the DPA path doing this", that
skill is the next stop.
doca-flow-perf — the
host / DPU-CPU Flow performance tool. The cross-tool
comparison rule lives in
CAPABILITIES.md ## Capabilities and modes:
name which tool produced which number.
doca-flow-tune — the Flow
tuning tool. A DPA-perf number is the kind of baseline
doca-flow-tune then optimizes on top of, via a Flow-program
modify-a-sample loop.
doca-public-knowledge-map —
routing to the public DOCA Flow DPA Perf page on
docs.nvidia.com and the rest of the public DOCA
documentation set.
doca-version — canonical
DOCA version-handling rules. The
## Version compatibility
section in this skill is a thin overlay on top.
doca-setup — env preparation,
install verification, hugepages, NUMA awareness, and the
I have no install yet path with the public NGC DOCA
container.
doca-debug — the cross-cutting
debug ladder. DPA-perf surfaces its own error taxonomy;
when the cause turns out to be below DOCA, the taxonomy
hands off to doca-debug.
doca-hardware-safety —
the cross-cutting hardware-safety meta-policy this skill's
## Safety policy overlays.
1---2license: Apache-2.03name: doca-flow-dpa-perf4description: >5 Use this skill when the user is invoking doca_flow_dpa_perf on6 DPA-capable hardware (ConnectX-7 minimum supported,7 ConnectX-8 recommended, or BlueField-3) to measure rule8 update / disable rates on the DPA-offloaded DOCA Flow path —9 picking the active / passive device split, choosing workload-shape10 axes (burst, queue, completion threshold, workers, hash pipe algo,11 PSL tables), or reading Kops/sec iteration stats and the optional12 self-test. Trigger even when the user does not explicitly mention13 "doca_flow_dpa_perf" or "DPA Provider" — typical implicit phrasings14 include "how fast can the DPA program path-selector entries",15 "baseline rule-update rate on ConnectX-8", "tool reports zero ops16 on my BlueField", "self-test sentinel never shows on tcpdump", or17 "is my BlueField-2 DPA-capable". Refuse and route elsewhere for the18 host / DPU-CPU Flow path (doca-flow-perf), Flow pipeline tuning19 (doca-flow-tune), writing doca-flow / doca-dpa applications, or20 DOCA install — those belong to other skills.21metadata:22 source: https://skillmd.com/skills/nvidia/doca-flow-dpa-perf23 kind: tool24compatibility: >25 Requires DOCA SDK installed at /opt/mellanox/doca on Linux (Ubuntu26 22.04/24.04 or RHEL/SLES) with a DPA-capable device attached —27 ConnectX-7 as the minimum supported ConnectX generation,28 ConnectX-8 recommended, or BlueField-3 (BlueField-2 and earlier29 ConnectX are unsupported). VNF Flow mode required; PF or VF only (SFs are not30 supported on the DPA path). Reads `pkg-config doca-flow` and the31 shipped `doca_flow_dpa_perf` binary plus its README on the user's32 install.33---3435# DOCA Flow DPA Perf (`doca_flow_dpa_perf`)3637**Where to start:** This is a tool skill for invoking38`doca_flow_dpa_perf`, the DPA-accelerated Flow performance tool.39Open [`TASKS.md`](TASKS.md) and start at40[`## configure`](TASKS.md#configure) to confirm DPA-capable41hardware + VNF Flow mode + the active / passive device split, then42[`## run`](TASKS.md#run) for the smoke-before-bulk flow with a43small operation count before any sweep, then44[`## test`](TASKS.md#test) for the eval-loop overlay that gates45defensible Kops/sec numbers. Open [`CAPABILITIES.md`](CAPABILITIES.md)46when the question is *what `doca_flow_dpa_perf` can measure*,47*what the DPA preconditions are*, *which devices it runs on*,48or *how to interpret update / disable / self-test output without49fooling yourself*. If DOCA is not installed yet, route to50[`doca-setup`](../../doca-setup/SKILL.md) first; if the device is51not DPA-capable (no ConnectX-7+ or BlueField-3+) then this tool is52the wrong surface and the right answer is53[`doca-flow-perf`](../doca-flow-perf/SKILL.md).5455## Example questions this skill answers well5657The CLASSES of `doca_flow_dpa_perf` questions this skill is built58to answer, each with one worked example. The class is the59load-bearing piece; the worked example is one instance.6061- **"Should I measure the DPA-offloaded Flow path or the62 host / DPU-CPU Flow path for this question?"** — worked63 example: *"my workload programs path-selector entries via64 DOCA Flow; do I baseline with `doca_flow_dpa_perf` or with65 `doca_flow_perf`?"*. Answered by the *DPA-vs-host* boundary66 in67 [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes)68 and the device-preconditions table.69- **"What does the DPA-offload actually accelerate, and what70 doesn't it change?"** — worked example: *"if I move my Flow71 rule update path to the DPA, what changes in the data plane72 for the packets themselves?"*. Answered by the DPA-Provider73 scope in74 [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes).75- **"What hardware do I need to use this tool at all?"** —76 worked example: *"is my BlueField-2 DPA-capable?"*. Answered77 by the device-preconditions table in78 [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes)79 (BlueField-3 yes, BlueField-2 no; ConnectX-7 minimum80 supported, ConnectX-8 recommended, and later generations81 supported per the public guide and the82 shipped README on the user's install).83- **"How do I size my run — burst, queue, completion threshold,84 number of operations, iterations — to get a defensible85 Kops/sec number?"** — worked example: *"I want the median86 iteration time and standard deviation, not a single noisy87 first-iteration spike"*. Answered by the eval-loop overlay88 in89 [`TASKS.md ## test`](TASKS.md#test) and the iteration-stats90 rule in91 [`CAPABILITIES.md ## Observability`](CAPABILITIES.md#observability).92- **"My tool reports zero ops / hangs / fails the self-test —93 what does that mean?"** — worked example: *"the tool runs but94 the self-test step fails"*. Answered by the layered error95 taxonomy in96 [`CAPABILITIES.md ## Error taxonomy`](CAPABILITIES.md#error-taxonomy)97 + the debug ladder in98 [`TASKS.md ## debug`](TASKS.md#debug).99- **"How do I quote a DPA-perf number alongside a host-side100 Flow-perf number for the same workload, in a way the next101 engineer can actually compare?"** — worked example: *"two102 Kops/sec numbers for what is supposedly the same workload"*.103 Answered by the four-tuple capture rule in104 [`CAPABILITIES.md ## Safety policy`](CAPABILITIES.md#safety-policy)105 + the per-tool-name rule (the host tool and the DPA tool are106 different surfaces; their numbers are not interchangeable107 without naming which tool produced which).108109## Audience110111This skill serves **external operators, performance engineers,112DOCA Flow application developers, and AI agents who need a113defensible measurement of the DPA-offloaded Flow update path** on114DPA-capable hardware. Concretely:115116- A platform operator deciding whether to move a path-selector117 workload onto the DPA versus keeping it on the host / DPU-CPU118 path, and wanting a number to compare.119- A performance engineer producing a *"DPA Kops/sec for update120 operation, queue-size X, burst-size Y, N workers"* baseline121 on a specific device + DOCA version so a downstream122 comparison is meaningful.123- A DOCA Flow application developer who has already used124 `doca-dpa` to land a DPA-offload of their Flow rule update125 path and wants to characterize what the device delivers.126- An AI agent answering *"what update rate should I expect from127 the DPA-offloaded Flow path on device Y?"* honestly — with a128 measured number, the command line that produced it, and the129 device + DOCA version + as-deployed environment that scopes130 it — instead of guessing from datasheet headlines.131132It is **not** for users debugging the tool's source code,133**not** a substitute for the live public DOCA Flow DPA Perf guide134on `docs.nvidia.com`, **not** the place to learn the `doca-flow`135or `doca-dpa` APIs (that audience belongs in136[`doca-flow`](../../libs/doca-flow/SKILL.md) and137`doca-dpa`), and **not** the right138tool for the host / DPU-CPU Flow path (route to139[`doca-flow-perf`](../doca-flow-perf/SKILL.md)).140141`doca_flow_dpa_perf` is shipped as a **single CLI binary** with142DPA-side device code linked in. The skill uses the same143`kind: tool` three-file shape as the rest of the bundle so144the agent's task-verb contract is uniform across the bundle.145146## Language scope147148This skill governs invocation, output interpretation, and149recommendation-of-routing for the `doca_flow_dpa_perf` CLI on150DPA-capable hardware. The tool itself has both a host-side151control (C-language ARGP + DOCA + DPDK code per the shipped152`flow_dpa_perf.c` / `flow_dpa_perf_core.c`) and a DPA-side device153component (DPA-side code on the shipped DPA device runtime).154External users do not link any of this; what they configure is155the JSON-config-or-CLI invocation surface. For the156`doca-dpa` programming model behind the DPA-side execution157engine, see158`doca-dpa`; for the `doca-flow`159API behind the pipeline the DPA path executes, see160[`doca-flow`](../../libs/doca-flow/SKILL.md).161162## When to load this skill163164Load this skill when the user is — or the agent needs to —165invoke `doca_flow_dpa_perf` on a real host with DOCA installed166and a DPA-capable device attached (or the public NGC DOCA167container with the equivalent device passthrough) to measure168update / disable rates on the DPA-offloaded Flow path.169Concretely:170171- Confirming DPA preconditions (DPA-capable device class,172 VNF Flow mode, recommended PF use, no SFs) before invoking173 the tool.174- Picking the active / passive device split appropriate to the175 user's hardware (two-port BlueField-3 active + passive; one-176 port ConnectX-9 active only).177- Picking the workload-shape axes (burst size, queue size,178 completion threshold, hash pipe algorithm, work policy,179 number of PSL tables, table size, number of workers).180- Picking the operation axis (update or disable-enable) per the181 shipped README's documented operations.182- Producing a defensible Kops/sec number with iteration stats183 (median, max, standard deviation) captured.184- Diagnosing zero-ops / hung / failed-self-test runs through185 the layered error taxonomy.186187Do **not** load this skill for general DOCA orientation, Flow188program API work, or installation. For those, use189[`doca-public-knowledge-map`](../../doca-public-knowledge-map/SKILL.md),190the matching `libs/<library>` skill, or191[`doca-setup`](../../doca-setup/SKILL.md). Do not load it for192the host / DPU-CPU Flow path — that audience belongs in193[`doca-flow-perf`](../doca-flow-perf/SKILL.md).194195## What this skill provides196197This is a **thin loader**. Substantive material lives in two198companion files:199200- `CAPABILITIES.md` — what `doca_flow_dpa_perf` measures201 (the DPA-Provider-on-DPA-device update / disable path202 specifically), the DPA-vs-host-path boundary, the203 device-preconditions table (ConnectX-7+ / BlueField-3+),204 the documented VNF-only Flow-mode rule, the PF-vs-VF-vs-SF205 rule (SFs not supported on DPA), the workload-shape axes206 (burst, queue, completion threshold, hash pipe algorithm,207 work policy, PSL tables, table size, workers), the208 operation axis (update vs disable-enable), the version209 overlay (this tool rides the `doca-flow` and `doca-dpa`210 versions it links against; the canonical rules live in211 [`doca-version`](../../doca-version/SKILL.md)), the layered212 error taxonomy213 (config-syntax / device-binding / dpa-precondition /214 workload-precondition / measurement-soundness / self-test /215 version / cross-cutting), the observability surface216 (iteration statistics, self-test path-selector verification,217 tcpdump-side traffic verification), and the safety posture218 (smoke-before-bulk, four-tuple capture, name the tool that219 produced the number).220- `TASKS.md` — step-by-step workflows for the in-scope task221 verbs: `install` (route to setup; the binary is shipped),222 `configure` (DPA-preconditions + active / passive device +223 workload-shape decision), `build` (route to install — the224 binary is shipped), `modify` (refuse — modify the invocation,225 not the binary), `run` (smoke before bulk), `test` (eval226 loop), `debug` (layered diagnosis), `use` (consume the227 captured number), plus a `Deferred task verbs` block routing228 out-of-scope questions and a `Command appendix`.229230The skill assumes a host where DOCA is already installed (or231the NGC DOCA container is running) on a DPA-capable device and232the operator has the permissions to bind the device and allocate233the DPA execution resources the tool needs.234235## What this skill deliberately does not ship236237This skill is **agent guidance**, not a samples or scripts238bundle. To keep the boundary clean, it deliberately does not239contain — and pull requests should not add:240241- **Verbatim default values for flag inventories beyond what242 the shipped README or installed `--help` documents.** Read243 defaults from the README first, then fall back to the244 installed binary's `--help`. If neither defines a needed245 default, stop and request the operator's explicit value246 instead of guessing. The247 flag surface is install-specific within the documented248 surface; the documented invocations + `--help` on the249 installed version are the authoritative answer. Inventing250 a flag is the most common hallucination failure.251- **Pre-baked example Kops/sec numbers or expected throughput252 numbers.** Output is device-, firmware-, DOCA-version-,253 workload-, and platform-specific; a pinned number for one254 platform misleads operators on a different platform /255 version. The shipped README's example numbers are256 *illustrative*, not a baseline the agent should quote as257 ground truth.258- **Wrappers, parsers, or scripts** in any language that259 consume the tool's stdout / CSV. The output format is260 documented; if a user wants to script against it, the261 right answer is "read the live guide, write the parser262 against your installed version".263- **A `samples/` or `reference/` subtree.** This is a thin264 loader for a documented CLI; substantive material lives on265 the public page, in `--help`, and in the shipped README on266 the user's install.267268## Loading order2692701. Read this `SKILL.md` first to confirm the user's question271 is in scope (the user actually wants to invoke272 `doca_flow_dpa_perf` on DPA-capable hardware, not measure273 the host / DPU-CPU Flow path).2742. **For what `doca_flow_dpa_perf` measures, the DPA-vs-host275 boundary, the device-preconditions table, the workload-276 shape axes, the version overlay, the error taxonomy, the277 observability surface, and the safety posture, see278 [CAPABILITIES.md](CAPABILITIES.md).**2793. **For the documented invocations and the smoke-before-bulk280 workflow — `install`, `configure`, `build`, `modify`,281 `run`, `test`, `debug`, `use` — see [TASKS.md](TASKS.md).**282283## Related skills284285- [`doca-flow`](../../libs/doca-flow/SKILL.md) — the **base286 library** whose pipeline this tool measures on the DPA287 path. The pipe / entry / rule surface this tool drives is288 created by `doca-flow` program code; the library's pipe289 attributes and capability surface are the upstream context.290- `doca-dpa` — the291 programming model behind the DPA execution engine the tool292 runs on. When the user's question goes from *"measure the293 DPA path"* to *"why is the DPA path doing this"*, that294 skill is the next stop.295- [`doca-flow-perf`](../doca-flow-perf/SKILL.md) — the296 host / DPU-CPU Flow performance tool. The cross-tool297 comparison rule lives in298 [`CAPABILITIES.md ## Capabilities and modes`](CAPABILITIES.md#capabilities-and-modes):299 name which tool produced which number.300- [`doca-flow-tune`](../doca-flow-tune/SKILL.md) — the Flow301 tuning tool. A DPA-perf number is the kind of baseline302 `doca-flow-tune` then optimizes on top of, via a Flow-program303 modify-a-sample loop.304- [`doca-public-knowledge-map`](../../doca-public-knowledge-map/SKILL.md) —305 routing to the public DOCA Flow DPA Perf page on306 `docs.nvidia.com` and the rest of the public DOCA307 documentation set.308- [`doca-version`](../../doca-version/SKILL.md) — canonical309 DOCA version-handling rules. The310 [`## Version compatibility`](CAPABILITIES.md#version-compatibility)311 section in this skill is a thin overlay on top.312- [`doca-setup`](../../doca-setup/SKILL.md) — env preparation,313 install verification, hugepages, NUMA awareness, and the314 *I have no install yet* path with the public NGC DOCA315 container.316- [`doca-debug`](../../doca-debug/SKILL.md) — the cross-cutting317 debug ladder. DPA-perf surfaces *its own* error taxonomy;318 when the cause turns out to be below DOCA, the taxonomy319 hands off to `doca-debug`.320- [`doca-hardware-safety`](../../doca-hardware-safety/SKILL.md) —321 the cross-cutting hardware-safety meta-policy this skill's322 `## Safety policy` overlays.