RTE_EVENT_VECTOR_ADAPTER(3)

✨ NAME ✨

rte_event_vector_adapter — bestie, this is the vector adapter structure from DPDK's library functions, and she's here to hold all your adapter tea 💅

---

🌸 SYNOPSIS 🌸

#include <rte_event_vector_adapter.h>

🎀 Data Fields 🎀

• rte_event_vector_adapter_enqueue_t enqueue
• struct rte_event_vector_adapter_data * data
• const struct event_vector_adapter_ops * ops
• uint32_t adapter_id
• uint8_t used: 1

---

🦋 Detailed Description 🦋

It's giving vector adapter structure, periodt. That's the whole vibe. She lives at Definition at line 228 of file rte_event_vector_adapter.h — iconic address, no cap 📍

---

👑 Field Documentation 👑

💖 rte_event_vector_adapter_enqueue_t enqueue

A pointer to the driver's enqueue function. Like, she's the girl who actually does the thing 🔥

Definition at line 229 of file rte_event_vector_adapter.h.

🍓 struct rte_event_vector_adapter_data* data

A pointer to the adapter data. All the lore lives here, fr fr 💾

Definition at line 231 of file rte_event_vector_adapter.h.

🧚 const struct event_vector_adapter_ops* ops

The functions exported by the adapter driver. Her little toolkit of tricks ✨

Definition at line 233 of file rte_event_vector_adapter.h.

💜 uint32_t adapter_id

The identifier of the adapter instance. Every adapter needs her own name tag so nobody gets confused at the function 🏷️

Definition at line 236 of file rte_event_vector_adapter.h.

🌈 uint8_t used

Flag to indicate that this adapter is being used. Yes queen, she's booked and busy 💅

Definition at line 238 of file rte_event_vector_adapter.h.

---

🫶 Author 🫶

Generated automatically by Doxygen for DPDK from the source code. Not a human author situation, bestie — the robots did this one and honestly? They ate 🤖💖

---

okay that's the whole page!! every field, every line number, all of it 🌸 go forth and vector your adapters, iykyk ⭐

This was rte_event_vector_adapter(3) from DPDK, Version 25.11.3 — mwah, typing to you from the DPDK manual pages 💌 byeee 🎀