RTE_EVENT_CRYPTO_ADAPTER_CONF(3)

💖 rte_event_crypto_adapter_conf(3) 💖

okay bestie, welcome to section 3 of the library functions manual — we're doing rte_event_crypto_adapter_conf today and it's literally the glow-up your event crypto adapter config has been waiting for 🫶

---

✨ NAME ✨

rte_event_crypto_adapter_conf — the adapter configuration struct, no cap

---

🌸 SYNOPSIS 🌸

#include <rte_event_crypto_adapter.h>

🎀 Data Fields

• uint8_t event_port_id
• uint32_t max_nb

---

🦋 DESCRIPTION 🦋

So. This is the adapter configuration structure — the one that the adapter configuration callback function is expected to fill out. That's the whole job. It's giving "fill in the blanks and hand me back the vibes" 💅

See also: rte_event_crypto_adapter_conf_cb — go check that one out too, it's the callback doing the actual filling, iykyk.

Also for the record: this struct is Definition at line 246 of file rte_event_crypto_adapter.h. noted 📝

---

👑 FIELD DOCUMENTATION 👑

⭐ uint8_t event_port_id

Event port identifier, bestie. The adapter enqueues events to this port, and it dequeues crypto request events in RTE_EVENT_CRYPTO_ADAPTER_OP_FORWARD mode. That's the whole personality of this field 🔥

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 — and this is the important part, don't skip it — this isn't treated as a requirement. Batching may cause the adapter to process more than max_nb crypto ops. So it's like "at least this many, probably more, no promises" energy 😭

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 it by hand, the machines did that part 🤖✨

---

and that's the tea, queen 💜 you now know rte_event_crypto_adapter_conf through and through — go fill out that config callback and slay 🎀🦋🌸

signing off from DPDK, Version 25.11.3, manual page rte_event_...dapter_conf(3) — periodt. 💅