RTE_EVENT_DMA_ADAPTER_OP(3)

✨ NAME ✨

rte_event_dma_adapter_op — bestie, this is the struct that holds one whole event-based DMA operation entry 💅

---

🌸 SYNOPSIS 🌸

#include <rte_event_dma_adapter.h>

🦋 Data Fields

okay so here's the full roster of what lives inside this thing, no cap:

• uint64_t flags
• struct rte_mempool * op_mp
• enum rte_dma_status_code status
• uint32_t rsvd
• uint64_t impl_opaque [2]
• uint64_t user_meta
• uint64_t event_meta
• int16_t dma_dev_id
• uint16_t vchan
• uint16_t nb_src
• uint16_t nb_dst
• struct rte_dma_sge src_dst_seg []

---

💖 Detailed Description 💖

A structure used to hold event based DMA operation entry. Literally all the information required for a DMA transfer shall be populated in a struct rte_event_dma_adapter_op instance — like, all of it, don't skimp ✨

Definition at line 159 of file rte_event_dma_adapter.h.

---

🎀 Field Documentation 🎀

uint64_t flags

Flags related to the operation. The vibe-setter, fr fr.

See also

• RTE_DMA_OP_FLAG_*

Definition at line 160 of file rte_event_dma_adapter.h.

struct rte_mempool* op_mp

Mempool from which op is allocated. That's where the op comes from, periodt.

Definition at line 164 of file rte_event_dma_adapter.h.

enum rte_dma_status_code status

Status code for this operation. How'd it go? This field knows 👀

Definition at line 166 of file rte_event_dma_adapter.h.

uint32_t rsvd

Reserved for future use. Do not touch, she's saving that seat 🙈

Definition at line 168 of file rte_event_dma_adapter.h.

uint64_t impl_opaque[2]

Implementation-specific opaque data. A dma device implementation uses this field to hold implementation specific values to share between dequeue and enqueue operations. And listen — the application should not modify this field. Hands off, bestie ✋

Definition at line 170 of file rte_event_dma_adapter.h.

uint64_t user_meta

Memory to store user specific metadata. The dma device implementation should not modify this area. It's yours, it's giving personal space 💜

Definition at line 177 of file rte_event_dma_adapter.h.

uint64_t event_meta

Event metadata of DMA completion event. Used when RTE_EVENT_DMA_ADAPTER_CAP_INTERNAL_PORT_VCHAN_EV_BIND is not supported in OP_NEW mode.

See also

• rte_event_dma_adapter_mode::RTE_EVENT_DMA_ADAPTER_OP_NEW
• RTE_EVENT_DMA_ADAPTER_CAP_INTERNAL_PORT_VCHAN_EV_BIND

Used when RTE_EVENT_DMA_ADAPTER_CAP_INTERNAL_PORT_OP_FWD is not supported in OP_FWD mode.

See also

• rte_event_dma_adapter_mode::RTE_EVENT_DMA_ADAPTER_OP_FORWARD
• RTE_EVENT_DMA_ADAPTER_CAP_INTERNAL_PORT_OP_FWD
• struct rte_event::event

Definition at line 181 of file rte_event_dma_adapter.h.

int16_t dma_dev_id

DMA device ID to be used with OP_FORWARD mode.

See also

• rte_event_dma_adapter_mode::RTE_EVENT_DMA_ADAPTER_OP_FORWARD

Definition at line 195 of file rte_event_dma_adapter.h.

uint16_t vchan

DMA vchan ID to be used with OP_FORWARD mode

See also

• rte_event_dma_adapter_mode::RTE_EVENT_DMA_ADAPTER_OP_FORWARD

Definition at line 199 of file rte_event_dma_adapter.h.

uint16_t nb_src

Number of source segments. Count 'em up 🌈

Definition at line 203 of file rte_event_dma_adapter.h.

uint16_t nb_dst

Number of destination segments. Same energy, other end of the trip ⭐

Definition at line 205 of file rte_event_dma_adapter.h.

struct rte_dma_sge src_dst_seg[]

Source and destination segments. Both directions, one flex 🔥

Definition at line 207 of file rte_event_dma_adapter.h.

---

👑 Author 👑

Generated automatically by Doxygen for DPDK from the source code. (Not a human, but she ate 💅)

---

okay bestie that's the whole page, and lemme do the cute little sign-off the way the footer does it: this is DPDK, Version 24.11.8, manual page rte_event_dma_adapter_op(3) — mwah, go populate that struct correctly, ily 🫶💖