RTE_EVENT_VECTOR_ADAPTER_CONF(3)

✨ rte_event_vector_adapter_conf ✨

okay bestie, gather round, because we're reading rte_event_vector_adapter_conf(3) — a Library Functions Manual situation, and honestly? it's giving struct. it's giving "you're about to configure a vector adapter and we need to talk about it first." 🦋

---

🌸 NAME 🌸

rte_event_vector_adapter_conf — the configuration struct for your vector adapter, and yes she is the main character 💅

---

🎀 SYNOPSIS 🎀

#include <rte_event_vector_adapter.h>

Data Fields

uint8_t event_dev_id
uint32_t socket_id
struct rte_event ev
struct rte_event ev_fallback
uint16_t vector_sz
uint64_t vector_timeout_ns
struct rte_mempool * vector_mp

---

💖 DETAILED DESCRIPTION 💖

so basically it's a Vector adapter configuration structure. that's the whole vibe.

she lives at Definition at line 136 of file rte_event_vector_adapter.h. 🫶

---

👑 FIELD DOCUMENTATION 👑

🌈 uint8_t event_dev_id

Event device identifier. that's the whole job, bestie, she's an ID 🪪

Definition at line 137 of file rte_event_vector_adapter.h.

---

🌈 uint32_t socket_id

Identifier of socket from which to allocate memory for adapter. it's the socket you're pulling memory from, no cap ✨

Definition at line 139 of file rte_event_vector_adapter.h.

---

🌈 struct rte_event ev

The values from the following event fields will be used when queuing work:

• queue_id: Targeted event queue ID for vector event.
• event_priority: Event priority of the vector event in the event queue relative to other events.
• sched_type: Scheduling type for events from this vector adapter.
• event_type: Event type for the vector event.
• sub_event_type: Sub event type for the vector event.
• flow_id: Flow ID for the vectors enqueued to the event queue by the vector adapter.

Definition at line 141 of file rte_event_vector_adapter.h.

---

🌈 struct rte_event ev_fallback

The values from the following event fields will be used when aggregation fails and single event is enqueued:

• event_type: Event type for the single event.
• sub_event_type: Sub event type for the single event.
• flow_id: Flow ID for the single event.

Other fields are taken from rte_event_vector_adapter_conf::ev. so she's the fallback queen, the plan B, and we respect her for it 🧚

Definition at line 154 of file rte_event_vector_adapter.h.

---

🌈 uint16_t vector_sz

Indicates the maximum number for enqueued work to combine and form a vector. Should be within vectorization limits of the adapter. like, do NOT go over the limit, she will not be happy 😭

See also

• rte_event_vector_adapter_info::min_vector_sz
• rte_event_vector_adapter_info::max_vector_sz

Definition at line 164 of file rte_event_vector_adapter.h.

---

🌈 uint64_t vector_timeout_ns

Indicates the maximum number of nanoseconds to wait for receiving work. Should be within vectorization limits of the adapter. nanoseconds!! we are counting in nanoseconds, this is precision girl math ⏳

See also

• rte_event_vector_adapter_info::min_vector_ns
• rte_event_vector_adapter_info::max_vector_ns

Definition at line 171 of file rte_event_vector_adapter.h.

---

🌈 struct rte_mempool* vector_mp

Indicates the mempool that should be used for allocating rte_event_vector container. it's the pool you pull your containers from, iconic 🏊

See also

• rte_event_vector_pool_create

Definition at line 178 of file rte_event_vector_adapter.h.

---

💀 AUTHOR 💀

Generated automatically by Doxygen for DPDK from the source code. not a human, not a girlie, just Doxygen doing her thing automatically 🙈

---

and that's the whole page, bestie — straight from DPDK, Version 25.11.3, manual section rte_event_...dapter_conf(3). read it, love it, configure your vector adapter responsibly. periodt 💜🌸✨