RTE_EVENT_CRYPTO_ADAPTER_QUEUE_CONF(3)

💖 rte_event_crypto_adapter_queue_conf(3) — Library Functions Manual 💖

okay bestie, pull up a chair, we're doing a manual page from the DPDK family, and honestly? it's giving "small struct, enormous responsibilities." no cap. 🌸

---

✨ NAME ✨

rte_event_crypto_adapter_queue_conf — the struct that holds all your queue configuration vibes for the event crypto adapter. she's a struct. she's a whole personality. 🎀

---

🌈 SYNOPSIS 🌈

#include <rte_event_crypto_adapter.h>

📦 Data Fields

• uint32_t flags
• struct rte_event ev
• uint16_t vector_sz
• uint64_t vector_timeout_ns
• struct rte_mempool * vector_mp

---

🦋 Detailed Description 🦋

so this is the Adapter queue configuration structure. that's it, that's the whole description. she configures a queue for the adapter. lowkey iconic, highkey essential. 💅

heads up though (iykyk): this struct is Definition at line 293 of file rte_event_crypto_adapter.h. 📍

---

💜 Field Documentation 💜

🍓 uint32_t flags

Flags for handling crypto operations. yes ma'am, this is where you tell the adapter how to behave. 🫶

See also: RTE_EVENT_CRYPTO_ADAPTER_EVENT_VECTOR

Definition at line 294 of file rte_event_crypto_adapter.h. 📍

---

🧚 struct rte_event ev

If HW supports cryptodev queue pair to event queue binding, application is expected to fill in event information. so like — if your hardware is that girl and can bind a cryptodev queue pair to an event queue, then you have to actually populate the event info here. no skipping homework bestie. 😭

See also: RTE_EVENT_CRYPTO_ADAPTER_CAP_INTERNAL_PORT_QP_EV_BIND

Definition at line 298 of file rte_event_crypto_adapter.h. 📍

---

⭐ uint16_t vector_sz

Indicates the maximum number for crypto operations to combine and form a vector. she's the cap on how many crypto ops get squished together into one cute little vector. 🌈

See also:

• rte_event_crypto_adapter_vector_limits::min_sz
• rte_event_crypto_adapter_vector_limits::max_sz

valid only when the RTE_EVENT_CRYPTO_ADAPTER_EVENT_VECTOR flag is set in rte_event_crypto_adapter_queue_conf::flags. no flag, no vibes. periodt.

Definition at line 303 of file rte_event_crypto_adapter.h. 📍

---

🔥 uint64_t vector_timeout_ns

Indicates the maximum number of nanoseconds to wait for aggregating crypto operations. Should be within vectorization limits of the adapter. basically: how long am I willing to stand here holding these ops waiting for friends to show up. ⏳✨ and bestie — stay within the adapter's vectorization limits, that part is not optional.

See also:

• rte_event_crypto_adapter_vector_limits::min_timeout_ns
• rte_event_crypto_adapter_vector_limits::max_timeout_ns

valid only when the RTE_EVENT_CRYPTO_ADAPTER_EVENT_VECTOR flag is set in rte_event_crypto_adapter_queue_conf::flags. 🚨

Definition at line 311 of file rte_event_crypto_adapter.h. 📍

---

👑 struct rte_mempool* vector_mp

Indicates the mempool that should be used for allocating rte_event_vector container. Should be created by using rte_event_vector_pool_create. yup, this is the mempool doing the container allocation. and please, please, make it with rte_event_vector_pool_create — don't just grab any mempool off the shelf, that's not the vibe. 🙈

See also: rte_event_crypto_adapter_queue_conf::flags.

valid when the RTE_EVENT_CRYPTO_ADAPTER_EVENT_VECTOR flag is set in... yep, you guessed it, the same field. 💀

Definition at line 321 of file rte_event_crypto_adapter.h. 📍

---

💫 Author 💫

Generated automatically by Doxygen for DPDK from the source code. so no, a human did not lovingly hand-type this, the robots did it. respect to the robots fr fr. 🤖💖

---

aaand that's the whole page bestie!! thanks for reading, you ate that. mwah 💅💖✨

this was DPDK, Version 25.11.3, and the page lives at rte_event_..._queue_conf(3) — catch you on the next manual page, love u, bye!! 🎀🦋🌸