RTE_EVENT_ETH_RX_ADAPTER_CONF(3)

💖 rte_event_eth_rx_adapter_conf 💖

okay bestie, so this is the manual page for rte_event_eth_rx_adapter_conf — it lives in the DPDK library functions section, and it's basically a little struct-shaped love letter 🎀 that the adapter config callback has to fill in. let's get into it.

---

✨ NAME ✨

rte_event_eth_rx_adapter_conf — the adapter configuration struct, no cap 🫶

---

🌸 SYNOPSIS 🌸

#include <rte_event_eth_rx_adapter.h>

🦋 Data Fields

• uint8_t event_port_id
• uint32_t max_nb_rx

---

💅 DESCRIPTION 💅

so like, <hotpink>Detailed Description</hotpink> — this is an Adapter configuration structure that the adapter configuration callback function is expected to fill out. that's the whole vibe. it's a struct you hand over, the callback does its little thing, and everybody moves on ✨

See also

• rte_event_eth_rx_adapter_conf_cb

Definition at line 118 of file rte_event_eth_rx_adapter.h.

---

👑 FIELD DOCUMENTATION 👑

🌈 uint8_t event_port_id

literally just the Event port identifier — the adapter enqueues mbuf events to this port. that's it. that's the field. she's simple, she's iconic 💖

Definition at line 119 of file rte_event_eth_rx_adapter.h.

---

🍓 uint32_t max_nb_rx

okay so the adapter can return early if it has processed at least max_nb_rx mbufs. lowkey important caveat incoming though — 🚨 this isn't treated as a requirement 🚨. batching may cause the adapter to process more than max_nb_rx mbufs. so don't come for her if the number goes over, that's just how batching works bestie 💀

Definition at line 123 of file rte_event_eth_rx_adapter.h.

---

🧚 AUTHOR 🧚

Generated automatically by Doxygen for DPDK from the source code. she didn't write herself, the robots did it for her 🤖💅

---

DPDK Version 25.11.3 — and that's a wrap on rte_event_...dapter_conf(3) 🎀 mwah, go read the actual header, ily, bye 🫶✨