DOCA DPDK Bridge
Examples
- "How do I add DOCA Flow to my DPDK app?" — this is in
scope. Bind the DPDK port with
doca_dpdk_port_probe; do not
rewrite the data-plane as native doca-eth.
- "DOCA_ERROR_NOT_FOUND on port registration." — check the
DPDK/DOCA matched-pair window before changing the probe call.
Instructions
Follow Loading order below. Open the tasks companion for configure /
probe / debug. Open the capabilities companion for port binding
and mbuf conversion. Do not open every companion file.
Where to start: This skill assumes DOCA is already installed,
DPDK is already installed, the user has an existing DPDK
application, and they want to add DOCA capabilities to it
in-place (most commonly DOCA Flow for hardware steering)
without migrating the data-plane to DOCA-native APIs. Open
the tasks companion if the user wants to do something
(configure / build / modify / run / test / debug); open
the capabilities companion when the question is what
the bridge can express on this version. If the user has not
installed DOCA yet, route to
doca-setup/SKILL.md first. If the user is
starting fresh (no DPDK code yet) and just wants line-rate
packet I/O against DOCA, route to
doca-eth/SKILL.md instead — the bridge exists
for the interop case, not the start-fresh case.
How to use this skill. Read this file, then search the companion file
for the ## <name> heading the question needs and read that whole section.
Answer completely from it, quoting only its symbols and commands. Do not
browse docs; use the entry points in doca-public-knowledge-map. Give
environment checks as commands for the user's DOCA host. For out-of-scope
requests, name the skill that owns them and stop.
Example questions this skill answers well
The CLASSES of DOCA DPDK Bridge 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.
- "I have a DPDK app — how do I add DOCA Flow rules to it
without rewriting the data-plane?" — worked example: "my
packet-processing app already drives mbufs through
rte_eth_*
ports; I want to install DOCA Flow steering rules on those
ports for HW offload". Answered by the bridge-vs-native
selection rule inCapabilities and modes
- the port-handover workflow in
configure step 3.
- "How do I make a DPDK port visible to DOCA?" — worked
example: "I have a DPDK port id from
rte_eth_dev_*; how does
DOCA see it". Answered by the DPDK-port-id ↔ doca_dev
mapping (doca_dpdk_port_probe / doca_dpdk_port_as_dev) inCapabilities and modes
bridge-objects table + the binding workflow inconfigure step 4.
- "How do I move packets between DPDK mbufs and DOCA bufs?" —
worked example: "DPDK delivers an
rte_mbuf to my fastpath; I
want a DOCA library to operate on the payload". Answered by
the mbuf ↔ DOCA-buf conversion shape inCapabilities and modes
- the conversion-step workflow in
modify.
- "Is the bridge even installed and is its DPDK compatible
with my DOCA?" — worked example: "
pkg-config --exists doca-dpdk-bridge returns failure on a host that has DPDK
separately installed". Answered by the version-coupling rule
inVersion compatibility
- the cap-check workflow in
configure step 1.
- "Should I be using
doca-dpdk-bridge or doca-eth?" —
worked example: "new project; I have not committed to DPDK
yet". Answered by the path-selection table inCapabilities and modes
bridge-vs-native row + the deferred-verbs note inDeferred task verbs.
- "What does this
DOCA_ERROR_* from a bridge call mean and
which layer caused it?" — worked example: "DOCA_ERROR_NOT_FOUND
on a port-registration call after the DPDK port came up
cleanly". Answered by the bridge overlay on the cross-library
taxonomy inError taxonomy
debug that escalates to
doca-debug/SKILL.md.
Audience
This skill serves external developers who already maintain a
DPDK-based packet-processing application — i.e., users whose
data-plane already drives rte_eth_* ports and rte_mbuf
buffers — and who want to add DOCA capabilities (most
commonly hardware steering via DOCA Flow) by linking the bridge
into the same process. It is not for users starting a fresh
DOCA-native project (route to doca-eth/SKILL.md)
and not for users running pure DPDK with no interest in DOCA
(no skill in this bundle applies). It is also not for NVIDIA
developers contributing to DOCA DPDK Bridge itself.
Language scope. DOCA DPDK Bridge ships as a C library with
pkg-config module name doca-dpdk-bridge (the agent must
confirm the spelling against the user's install via
pkg-config --exists doca-dpdk-bridge; some DOCA releases use a
slightly different module name and the agent must not guess).
The shipped samples are written in C. C and C++ consumers are
the canonical case; the worked examples in the tasks companion assume
that path. Other-language consumers (Rust, Go, Python, …)
typically do not use this bridge — DPDK itself is C-shaped, and
a non-C DPDK app is rare; if the user is in that minority, the
skill's contribution is to keep the port-handover, capability,
permission, and error-taxonomy guidance language-neutral and
route them to the public C ABI as the authoritative surface.
When to load this skill
Load this skill when the user is doing hands-on DOCA DPDK Bridge
work, in any language. Concretely:
- The user has an EXISTING DPDK application (their data-plane
already drives
rte_eth_dev_* ports and rte_mbuf buffers),
and they want to layer DOCA on top — adding DOCA Flow rules,
feeding packets into a DOCA accelerator (Compress, AES-GCM, …),
or wiring a DOCA service into the same process.
- The user needs to bind a DPDK port id to a
doca_dev (via
doca_dpdk_port_probe / doca_dpdk_port_as_dev) so DOCA Core
/ DOCA Flow can operate on the same physical port.
- The user needs to convert between DPDK mbufs and DOCA-bufs at
the data-plane boundary, and is asking about the conversion
helpers and their cost.
- The user is debugging a
DOCA_ERROR_* returned from a bridge
call (lifecycle vs. permission vs. capability vs. DPDK-port-not-
registered vs. mbuf-conversion-failed) and the layered DPDK ↔
DOCA stack underneath.
- The user is hitting cross-version pain: their DPDK install and
their DOCA install are not the matched pair the bridge expects.
- The user is asking "native
doca-eth or doca-dpdk-bridge?"
and the agent needs the path-selection rule.
Do not load this skill for general DOCA orientation, install
of DOCA itself, fresh DOCA-native packet I/O (use
doca-eth/SKILL.md), flow-rule programming on
its own (use doca-flow/SKILL.md), host ↔ DPU
control messaging (use doca-comch/SKILL.md),
or RDMA data movement (use doca-rdma/SKILL.md).
For DOCA documentation orientation, use
doca-public-knowledge-map/SKILL.md.
What this skill provides
This is a thin loader. The body keeps only the orientation
needed to pick the right next file. The substantive bridge-
specific material lives in two companion files:
- the capabilities companion — what the DOCA DPDK Bridge can express on
this version: the bridge-vs-native selection rule (when to
use
doca-dpdk-bridge vs native doca-eth), the
bridge-object surface (DPDK-port-id ↔ doca_dev mapping, the
doca_dpdk_mempool mbuf ↔ DOCA-buf conversion), the
capability-query surface (the single
doca_dpdk_cap_is_rep_port_supported), the bridge error taxonomy
(mapped onto the cross-library DOCA_ERROR_* set), the
observability surface (DPDK-side counters + DOCA-side PE
events), and the safety policy that gates the matched-pair
DPDK ↔ DOCA version coupling, the EAL-must-be-up
precondition, and DPDK-side privileges.
- the tasks companion — step-by-step workflows for the six in-scope
bridge verbs:
configure, build, modify, run, test,
debug. Plus a Deferred task verbs block that points
out-of-scope questions at the right next skill, and a
Command appendix of the recurring commands the agent
reaches for.
The skill assumes a host or BlueField where DOCA AND DPDK are
already installed at the standard locations and the user has the
privileges their public install profile expects (typically sudo
or mlnx-group membership for DOCA, plus the DPDK-side
privileges to mount hugepages, bind PCIe ports, and open the
target rte_eth device). It does not cover installing DOCA —
that path goes through doca-setup/SKILL.md;
it does not cover installing or learning DPDK itself — that
belongs in upstream DPDK documentation reachable via
doca-public-knowledge-map/SKILL.md.
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 DPDK Bridge application source code, in any
language. The verified bridge source code is the bridge
usage inside the shipped C DOCA Flow samples at
/opt/mellanox/doca/samples/doca_flow/ (e.g. flow_common.c,
which calls doca_dpdk_port_probe() / doca_dpdk_port_as_dev()),
plus the canonical reference applications that pair DPDK +
DOCA Flow (see
doca-public-knowledge-map/SKILL.md
for the reference-applications index). 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/SKILL.md,
layered with the bridge-specific overrides inmodify.
- Standalone build manifests (
meson.build,
CMakeLists.txt, Cargo.toml, …) parked inside the skill.
The agent constructs the build manifest in the user's project
directory against the user's installed DOCA + DPDK, where
pkg-config --modversion doca-dpdk-bridge and
pkg-config --modversion libdpdk are the source 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.
Loading order
- Read this skill first to confirm the user's question is
in scope (existing DPDK app + wants DOCA on top — not fresh).
- For the bridge capability matrix, the bridge-vs-native
selection rule, port-handover surface, capability-query rules,
error taxonomy, observability, and safety policy, see
the capabilities companion.
- For step-by-step workflows — configure, build, modify, run,
test, debug — see the tasks companion.
Both companion files cross-link to each other,
doca-version/SKILL.md for the canonical
DOCA version-handling rules,
doca-eth/SKILL.md for the start-fresh path that
is the bridge's deliberate alternative,
doca-flow/SKILL.md for the steering library
that is the most common reason to use this bridge in the first
place, and
doca-public-knowledge-map/SKILL.md
whenever the right answer is "look it up in the public docs or
the installed package layout" rather than "bridge-specific
guidance".
Related skills
doca-public-knowledge-map/SKILL.md —
the routing table for every public DOCA documentation source
and the on-disk layout of an installed DOCA package. The
bridge URL slug is DOCA-DPDK-Bridge. Reference applications
that pair DPDK + DOCA Flow (the canonical adopters of this
bridge) are reachable from the same map's reference-
applications index.
doca-setup/SKILL.md — env preparation,
install verification, hugepage mounts (DPDK requirement),
port-state checks (devlink dev show, ip link), permission
and group-membership requirements for opening a doca_dev
AND for binding PCIe ports under DPDK. This skill assumes its
preconditions are satisfied.
doca-version/SKILL.md — canonical
DOCA version-handling rules. This skill's ## Version compatibility cross-links the four-way match rule and adds
only the bridge-specific overlay (DPDK ↔ DOCA matched-pair
coupling).
doca-structured-tools-contract/SKILL.md —
the bundle's structured-tools precedence rule (detect / prefer
/ fall back / report). The Command appendix in
the tasks companion honors this contract.
doca-programming-guide/SKILL.md —
general DOCA programming patterns shared by every library:
the canonical pkg-config + meson build pattern, the
universal modify-a-shipped-sample first-app workflow, the
universal lifecycle, the cross-library DOCA_ERROR_*
taxonomy, and the program-side debug order. This skill layers
bridge specifics on top.
doca-eth/SKILL.md — the alternative path
for users starting fresh: pure DOCA-native queue I/O via
doca_eth_rxq / doca_eth_txq with no DPDK in the picture.
The bridge exists because migrating an existing DPDK app to
doca-eth is often the wrong tradeoff; for a new project
with no DPDK lock-in, doca-eth is the right choice.
doca-flow/SKILL.md — the steering library
that is the most common reason a DPDK app reaches for this
bridge. The bridge binds a DPDK port id to a doca_dev;
DOCA Flow programs steering rules onto that doca_dev. The two
libraries are designed to compose.
doca-debug/SKILL.md — the cross-cutting
debug ladder (install / version / build / link / runtime /
program / driver). Bridge-specific debug (DPDK ↔ DOCA version
drift, port-not-registered symptoms, mbuf-conversion failures)
overlays on top of that ladder.
1---2license: Apache-2.03name: doca-dpdk-bridge4description: >5 Use this skill when the user has an existing DPDK application and is6 adding DOCA capabilities in-place — most commonly DOCA Flow hardware7 steering — without rewriting the data-plane in DOCA-native form:8 binding a DPDK port id to a `doca_dev` (`doca_dpdk_port_probe` /9 `doca_dpdk_port_as_dev`), converting `rte_mbuf` ↔ `doca_buf`, querying10 `doca_dpdk_cap_is_rep_port_supported`, or debugging `DOCA_ERROR_*`11 from a bridge call. Trigger even without "DOCA DPDK Bridge": "how do I12 add DOCA Flow to my DPDK app", "make a DPDK port visible to DOCA",13 "the bridge loads but every operation returns errors", "pkg-config14 --exists doca-dpdk-bridge fails", or "DOCA_ERROR_NOT_FOUND on port15 registration". Route elsewhere for fresh DOCA-native packet I/O16 (doca-eth), flow-rule programming (doca-flow), DOCA or DPDK install17 (doca-setup), or RDMA data movement (doca-rdma).18metadata:19 source: https://skillmd.com/skills/nvidia/doca-dpdk-bridge20 author: NVIDIA <doca-feedback@nvidia.com>21 kind: library22 doca_version: "3.5"23 tags:24 - doca25 - dpdk26 - bridge27compatibility: >28 Requires DOCA SDK installed at /opt/mellanox/doca on Linux (Ubuntu29 22.04/24.04 or RHEL/SLES) with a BlueField DPU or ConnectX NIC30 attached, plus a separate DPDK install whose version falls within the31 bridge's matched-pair window. Reads the user's local install via32 `pkg-config doca-dpdk-bridge` and `pkg-config libdpdk`, and inspects33 /opt/mellanox/doca/{lib,include,samples,applications}. The validation34 steps require a live DOCA install.35---3637# DOCA DPDK Bridge3839## Examples4041- **"How do I add DOCA Flow to my DPDK app?"** — this is in42 scope. Bind the DPDK port with `doca_dpdk_port_probe`; do not43 rewrite the data-plane as native `doca-eth`.44- **"DOCA_ERROR_NOT_FOUND on port registration."** — check the45 DPDK/DOCA matched-pair window before changing the probe call.4647## Instructions4849Follow Loading order below. Open the tasks companion for configure /50probe / debug. Open the capabilities companion for port binding51and mbuf conversion. Do not open every companion file.5253**Where to start:** This skill assumes DOCA is already installed,54DPDK is already installed, the user has an **existing DPDK55application**, and they want to **add DOCA capabilities to it56in-place** (most commonly DOCA Flow for hardware steering)57without migrating the data-plane to DOCA-native APIs. Open58the tasks companion if the user wants to *do* something59(configure / build / modify / run / test / debug); open60the capabilities companion when the question is *what61the bridge can express* on this version. If the user has not62installed DOCA yet, route to63`doca-setup/SKILL.md` first. If the user is64**starting fresh** (no DPDK code yet) and just wants line-rate65packet I/O against DOCA, route to66`doca-eth/SKILL.md` instead — the bridge exists67for the interop case, not the start-fresh case.6869**How to use this skill.** Read this file, then search the companion file70for the `## <name>` heading the question needs and read that whole section.71Answer completely from it, quoting only its symbols and commands. Do not72browse docs; use the entry points in `doca-public-knowledge-map`. Give73environment checks as commands for the user's DOCA host. For out-of-scope74requests, name the skill that owns them and stop.7576## Example questions this skill answers well7778The CLASSES of DOCA DPDK Bridge questions this skill is built to79answer, each with one worked example. The agent should treat the80*class* as the load-bearing piece — the worked example is a81single instance.8283- **"I have a DPDK app — how do I add DOCA Flow rules to it84 without rewriting the data-plane?"** — worked example: *"my85 packet-processing app already drives mbufs through `rte_eth_*`86 ports; I want to install DOCA Flow steering rules on those87 ports for HW offload"*. Answered by the bridge-vs-native88 selection rule in89 ## Capabilities and modes90 + the port-handover workflow in91 ## configure step 3.92- **"How do I make a DPDK port visible to DOCA?"** — worked93 example: *"I have a DPDK port id from `rte_eth_dev_*`; how does94 DOCA see it"*. Answered by the DPDK-port-id ↔ `doca_dev`95 mapping (`doca_dpdk_port_probe` / `doca_dpdk_port_as_dev`) in96 ## Capabilities and modes97 bridge-objects table + the binding workflow in98 ## configure step 4.99- **"How do I move packets between DPDK mbufs and DOCA bufs?"** —100 worked example: *"DPDK delivers an `rte_mbuf` to my fastpath; I101 want a DOCA library to operate on the payload"*. Answered by102 the mbuf ↔ DOCA-buf conversion shape in103 ## Capabilities and modes104 + the conversion-step workflow in105 ## modify.106- **"Is the bridge even installed and is its DPDK compatible107 with my DOCA?"** — worked example: *"`pkg-config --exists108 doca-dpdk-bridge` returns failure on a host that has DPDK109 separately installed"*. Answered by the version-coupling rule110 in111 ## Version compatibility112 + the cap-check workflow in113 ## configure step 1.114- **"Should I be using `doca-dpdk-bridge` or `doca-eth`?"** —115 worked example: *"new project; I have not committed to DPDK116 yet"*. Answered by the path-selection table in117 ## Capabilities and modes118 bridge-vs-native row + the deferred-verbs note in119 ## Deferred task verbs.120- **"What does this `DOCA_ERROR_*` from a bridge call mean and121 which layer caused it?"** — worked example: *"`DOCA_ERROR_NOT_FOUND`122 on a port-registration call after the DPDK port came up123 cleanly"*. Answered by the bridge overlay on the cross-library124 taxonomy in125 ## Error taxonomy126 + the layered ladder in127 ## debug that escalates to128 `doca-debug/SKILL.md`.129130## Audience131132This skill serves **external developers who already maintain a133DPDK-based packet-processing application** — i.e., users whose134data-plane already drives `rte_eth_*` ports and `rte_mbuf`135buffers — and who want to **add DOCA capabilities** (most136commonly hardware steering via DOCA Flow) by linking the bridge137into the same process. It is *not* for users starting a fresh138DOCA-native project (route to `doca-eth/SKILL.md`)139and *not* for users running pure DPDK with no interest in DOCA140(no skill in this bundle applies). It is also not for NVIDIA141developers contributing to DOCA DPDK Bridge itself.142143**Language scope.** DOCA DPDK Bridge ships as a C library with144`pkg-config` module name `doca-dpdk-bridge` (the agent must145confirm the spelling against the user's install via146`pkg-config --exists doca-dpdk-bridge`; some DOCA releases use a147slightly different module name and the agent must not guess).148The shipped samples are written in C. C and C++ consumers are149the canonical case; the worked examples in the tasks companion assume150that path. Other-language consumers (Rust, Go, Python, …)151typically do not use this bridge — DPDK itself is C-shaped, and152a non-C DPDK app is rare; if the user is in that minority, the153skill's contribution is to keep the port-handover, capability,154permission, and error-taxonomy guidance language-neutral and155route them to the public C ABI as the authoritative surface.156157## When to load this skill158159Load this skill when the user is doing hands-on DOCA DPDK Bridge160work, in any language. Concretely:161162- The user has an EXISTING DPDK application (their data-plane163 already drives `rte_eth_dev_*` ports and `rte_mbuf` buffers),164 and they want to layer DOCA on top — adding DOCA Flow rules,165 feeding packets into a DOCA accelerator (Compress, AES-GCM, …),166 or wiring a DOCA service into the same process.167- The user needs to bind a DPDK port id to a `doca_dev` (via168 `doca_dpdk_port_probe` / `doca_dpdk_port_as_dev`) so DOCA Core169 / DOCA Flow can operate on the same physical port.170- The user needs to convert between DPDK mbufs and DOCA-bufs at171 the data-plane boundary, and is asking about the conversion172 helpers and their cost.173- The user is debugging a `DOCA_ERROR_*` returned from a bridge174 call (lifecycle vs. permission vs. capability vs. DPDK-port-not-175 registered vs. mbuf-conversion-failed) and the layered DPDK ↔176 DOCA stack underneath.177- The user is hitting cross-version pain: their DPDK install and178 their DOCA install are not the matched pair the bridge expects.179- The user is asking *"native `doca-eth` or `doca-dpdk-bridge`?"*180 and the agent needs the path-selection rule.181182Do **not** load this skill for general DOCA orientation, install183of DOCA itself, fresh DOCA-native packet I/O (use184`doca-eth/SKILL.md`), flow-rule programming on185its own (use `doca-flow/SKILL.md`), host ↔ DPU186control messaging (use `doca-comch/SKILL.md`),187or RDMA data movement (use `doca-rdma/SKILL.md`).188For DOCA documentation orientation, use189`doca-public-knowledge-map/SKILL.md`.190191## What this skill provides192193This is a **thin loader**. The body keeps only the orientation194needed to pick the right next file. The substantive bridge-195specific material lives in two companion files:196197- the capabilities companion — what the DOCA DPDK Bridge can express on198 this version: the bridge-vs-native selection rule (when to199 use `doca-dpdk-bridge` vs native `doca-eth`), the200 bridge-object surface (DPDK-port-id ↔ `doca_dev` mapping, the201 `doca_dpdk_mempool` mbuf ↔ DOCA-buf conversion), the202 capability-query surface (the single203 `doca_dpdk_cap_is_rep_port_supported`), the bridge error taxonomy204 (mapped onto the cross-library `DOCA_ERROR_*` set), the205 observability surface (DPDK-side counters + DOCA-side PE206 events), and the safety policy that gates the matched-pair207 DPDK ↔ DOCA version coupling, the EAL-must-be-up208 precondition, and DPDK-side privileges.209- the tasks companion — step-by-step workflows for the six in-scope210 bridge verbs: `configure`, `build`, `modify`, `run`, `test`,211 `debug`. Plus a `Deferred task verbs` block that points212 out-of-scope questions at the right next skill, and a213 `Command appendix` of the recurring commands the agent214 reaches for.215216The skill assumes a host or BlueField where DOCA AND DPDK are217already installed at the standard locations and the user has the218privileges their public install profile expects (typically sudo219or `mlnx`-group membership for DOCA, plus the DPDK-side220privileges to mount hugepages, bind PCIe ports, and open the221target `rte_eth` device). It does not cover installing DOCA —222that path goes through `doca-setup/SKILL.md`;223it does not cover installing or learning DPDK itself — that224belongs in upstream DPDK documentation reachable via225`doca-public-knowledge-map/SKILL.md`.226227## What this skill deliberately does not ship228229This skill is **agent guidance**, not a samples or templates230bundle. To keep the boundary clean, it deliberately does not231contain — and pull requests should not add:232233- **Pre-written DOCA DPDK Bridge application source code, in any234 language.** The verified bridge source code is the bridge235 usage inside the shipped C DOCA Flow samples at236 `/opt/mellanox/doca/samples/doca_flow/` (e.g. `flow_common.c`,237 which calls `doca_dpdk_port_probe()` / `doca_dpdk_port_as_dev()`),238 plus the canonical reference applications that pair DPDK +239 DOCA Flow (see240 `doca-public-knowledge-map/SKILL.md`241 for the reference-applications index). The agent's job is to242 route the user to those files and prescribe a minimum-diff243 modification on them via the universal modify-a-sample244 workflow in245 `doca-programming-guide/SKILL.md`,246 layered with the bridge-specific overrides in247 ## modify.248- **Standalone build manifests** (`meson.build`,249 `CMakeLists.txt`, `Cargo.toml`, …) parked inside the skill.250 The agent constructs the build manifest *in the user's project251 directory* against the user's installed DOCA + DPDK, where252 `pkg-config --modversion doca-dpdk-bridge` and253 `pkg-config --modversion libdpdk` are the source of truth.254- **A `samples/`, `bindings/`, or `reference/` subtree** of any255 kind. A mock or incomplete artifact in this skill's tree, even256 one labeled "reference", is misleading: users will read it as257 buildable.258259## Loading order2602611. Read this skill first to confirm the user's question is262 in scope (existing DPDK app + wants DOCA on top — not fresh).2632. **For the bridge capability matrix, the bridge-vs-native264 selection rule, port-handover surface, capability-query rules,265 error taxonomy, observability, and safety policy, see266 the capabilities companion.**2673. **For step-by-step workflows — configure, build, modify, run,268 test, debug — see the tasks companion.**269270Both companion files cross-link to each other,271`doca-version/SKILL.md` for the canonical272DOCA version-handling rules,273`doca-eth/SKILL.md` for the start-fresh path that274is the bridge's deliberate alternative,275`doca-flow/SKILL.md` for the steering library276that is the most common reason to use this bridge in the first277place, and278`doca-public-knowledge-map/SKILL.md`279whenever the right answer is "look it up in the public docs or280the installed package layout" rather than "bridge-specific281guidance".282283## Related skills284285- `doca-public-knowledge-map/SKILL.md` —286 the routing table for every public DOCA documentation source287 and the on-disk layout of an installed DOCA package. The288 bridge URL slug is `DOCA-DPDK-Bridge`. Reference applications289 that pair DPDK + DOCA Flow (the canonical adopters of this290 bridge) are reachable from the same map's reference-291 applications index.292- `doca-setup/SKILL.md` — env preparation,293 install verification, hugepage mounts (DPDK requirement),294 port-state checks (`devlink dev show`, `ip link`), permission295 and group-membership requirements for opening a `doca_dev`296 AND for binding PCIe ports under DPDK. This skill assumes its297 preconditions are satisfied.298- `doca-version/SKILL.md` — canonical299 DOCA version-handling rules. This skill's `## Version300 compatibility` cross-links the four-way match rule and adds301 only the bridge-specific overlay (DPDK ↔ DOCA matched-pair302 coupling).303- `doca-structured-tools-contract/SKILL.md` —304 the bundle's structured-tools precedence rule (detect / prefer305 / fall back / report). The Command appendix in306 the tasks companion honors this contract.307- `doca-programming-guide/SKILL.md` —308 general DOCA programming patterns shared by every library:309 the canonical `pkg-config` + meson build pattern, the310 universal modify-a-shipped-sample first-app workflow, the311 universal lifecycle, the cross-library `DOCA_ERROR_*`312 taxonomy, and the program-side debug order. This skill layers313 bridge specifics on top.314- `doca-eth/SKILL.md` — the **alternative path**315 for users starting fresh: pure DOCA-native queue I/O via316 `doca_eth_rxq` / `doca_eth_txq` with no DPDK in the picture.317 The bridge exists *because* migrating an existing DPDK app to318 `doca-eth` is often the wrong tradeoff; for a new project319 with no DPDK lock-in, `doca-eth` is the right choice.320- `doca-flow/SKILL.md` — the steering library321 that is the most common reason a DPDK app reaches for this322 bridge. The bridge binds a DPDK port id to a `doca_dev`;323 DOCA Flow programs steering rules onto that `doca_dev`. The two324 libraries are designed to compose.325- `doca-debug/SKILL.md` — the cross-cutting326 debug ladder (install / version / build / link / runtime /327 program / driver). Bridge-specific debug (DPDK ↔ DOCA version328 drift, port-not-registered symptoms, mbuf-conversion failures)329 overlays on top of that ladder.