rte_cryptodev_qp_conf(3)

💖 NAME 💖

rte_cryptodev_qp_conf — bestie, this is the queue pair configuration struct for a crypto device 🎀 like it's the lil form you fill out before your queue pair can even exist.

---

✨ SYNOPSIS ✨

#include <rte_cryptodev.h>

🦋 Data Fields 🦋

• uint32_t nb_descriptors
• struct rte_mempool * mp_session
• uint8_t priority

---

👑 Detailed Description 👑

Crypto device queue pair configuration structure. That's it, that's the whole vibe — it's the struct that holds all the settings for one queue pair. 💅

Definition at line 661 of file rte_cryptodev.h.

---

🌸 Field Documentation 🌸

uint32_t nb_descriptors

Number of descriptors per queue pair. That's how many descriptor slots each queue pair gets — your literal capacity, no cap fr fr. 🍓

Definition at line 662 of file rte_cryptodev.h.

struct rte_mempool* mp_session

The mempool for creating session in sessionless mode. So when you're running sessionless, this is the pool the sessions get pulled out of. 🫶

Definition at line 663 of file rte_cryptodev.h.

uint8_t priority

Priority for this queue pair relative to other queue pairs. Yes bestie, queue pairs have a hierarchy, main character energy only. 🌈

The requested priority should in the range of [RTE_CRYPTODEV_QP_PRIORITY_HIGHEST, RTE_CRYPTODEV_QP_PRIORITY_LOWEST]. The implementation may normalize the requested priority to device supported priority value.

So don't be out here shocked if the number you asked for isn't the number you get back — the device might round it to whatever it actually supports. Not a bug, just how it is. 🙈

Definition at line 665 of file rte_cryptodev.h.

---

💜 Author 💜

Generated automatically by Doxygen for DPDK from the source code. Not a human, just a very diligent robot earning its keep. ✨

---

okay that's the whole page!! 🎀 shoutout to DPDK, this is from Version 25.11.3, and the manual page name is rte_cryptodev_qp_conf(3) — mwah, go configure your queue pairs responsibly bestie 💖🦋