rte_crypto...pabilities(3)

✨ NAME ✨

rte_cryptodev_capabilities — bestie, this is the glow-up struct that holds a capability of a crypto device 💅 it's from the rte_crypto...pabilities(3) page in the Library Functions Manual section 3 (that's the "all the library functions live here" section, iykyk).

---

🌸 SYNOPSIS 🌸

#include <rte_cryptodev.h>

🎀 Data Fields

• enum rte_crypto_op_type op

---

🦋 DETAILED DESCRIPTION 🦋

okay so listen. this struct is literally the receipts for one single capability of a crypto device — like, "here's a thing this device can do" written down in a struct so the rest of DPDK can read it. no cap.

Definition at line 215 of file rte_cryptodev.h.

---

💖 FIELD DOCUMENTATION 💖

⭐ enum rte_crypto_op_type op

the operation type, like what kind of op this capability is talking about. it's giving "what are we even doing here" energy but as an enum. 🙈

Definition at line 216 of file rte_cryptodev.h.

🧚 struct rte_cryptodev_symmetric_capability sym

the symmetric operation capability parameters 🫶 everything symmetric-op-shaped about this capability goes right here.

Definition at line 220 of file rte_cryptodev.h.

🌈 struct rte_cryptodev_asymmetric_capability asym

the asymmetric operation capability parameters ✨ same vibe, other flavor of crypto — asymmetric ops store their capability details in this field.

Definition at line 222 of file rte_cryptodev.h.

---

👑 AUTHOR 👑

Generated automatically by Doxygen for DPDK from the source code. not a human writing this, just Doxygen doing its little machine thing 🤖💕

---

🌸💜 that's the whole page, bestie — and a lil sign-off for you: this was DPDK Version 25.11.3, section 3 of the manual, rte_crypto...pabilities(3). periodt. 💅✨