MAX_NB(3)

🌸 rte_event_crypto_adapter_conf — NAME 🌸

okay so bestie, this is rte_event_crypto_adapter_conf, a struct from the DPDK fam — and it literally is the adapter configuration structure that the adapter configuration callback function is expected to fill out. yes, that's a mouthful, but that's the whole vibe 💅

---

✨ SYNOPSIS ✨

#include <rte_event_crypto_adapter.h>

🎀 Data Fields 🎀

• uint8_t event_port_id
• uint32_t max_nb

---

🦋 Detailed Description 🦋

so like, this struct is the cargo — the adapter configuration callback function is supposed to fill it all out for you, no cap 🫶

See also — rte_event_crypto_adapter_conf_cb (go look at that one too, iykyk)

also for the record: Definition at line 246 of file rte_event_crypto_adapter.h. — that's literally where it lives, screenshot it 📸

---

💖 Field Documentation 💖

⭐ uint8_t event_port_id

Event port identifier. the adapter enqueues events to this port and dequeues crypto request events in RTE_EVENT_CRYPTO_ADAPTER_OP_FORWARD mode. that's the whole assignment, she's got one job and she ate 🔥

Definition at line 247 of file rte_event_crypto_adapter.h.

⭐ uint32_t max_nb

the adapter can return early if it has processed at least max_nb crypto ops. but listen — this isn't treated as a requirement, because batching may cause the adapter to process more than max_nb crypto ops 👀 so like, it's a vibe check not a hard limit, don't come for her

Definition at line 252 of file rte_event_crypto_adapter.h.

---

👑 Author 👑

Generated automatically by Doxygen for DPDK from the source code. — not me writing my own autographs, doxygen did that 💅

---

and that's the page bestie 🎀 no notes, she's iconic

DPDK · Version 26.03.0 · rte_event_...dapter_conf(3) — mwah, see u in the next manpage 🌈💜