RTE_CRYPTODEV_ASYMMETRIC_XFORM_CAPABILITY(3)

💖 rte_cryptodev_asymmetric_xform_capability 💖

okay bestie, so this is a page from the Library Functions Manual — specifically rte_crypto..._capability(3) — and it's literally all about rte_cryptodev_asymmetric_xform_capability. it's a struct, it lives in DPDK's cryptodev world, and it's here to tell you what your crypto device can and cannot do with asymmetric transforms. no cap, it's giving ✨spec sheet energy✨ and we're gonna read every single line of it together. 🫶

---

🌸 NAME 🌸

rte_cryptodev_asymmetric_xform_capability — the struct that spells out which asymmetric xform stuff your crypto device supports 👑

---

✨ SYNOPSIS ✨

#include <rte_cryptodev.h>

🎀 Data Fields 🎀

• enum rte_crypto_asym_xform_type xform_type
• uint32_t op_types
• uint64_t hash_algos

---

💅 Detailed Description 💅

Asymmetric Xform Crypto Capability

like. that's the whole vibe. it's the capability report card for asymmetric xforms. 📋

Definition at line 163 of file rte_cryptodev.h.

---

👑 Field Documentation 👑

🌈 enum rte_crypto_asym_xform_type xform_type

Transform type: RSA/MODEXP/DH/DSA/MODINV

so basically which flavor of transform we're talking about. pick your fighter: RSA, MODEXP, DH, DSA, or MODINV. 🥊

Definition at line 164 of file rte_cryptodev.h.

---

🌟 uint32_t op_types

Bitmask for supported rte_crypto_asym_op_type or rte_crypto_ml_kem_op_type or rte_crypto_ml_dsa_op_type or rte_crypto_asym_ke_type.

and bestie, the way you figure out which enum is in play is — plot twist — it's determined by the rte_crypto_asym_xform_type. 😭 here's the cheat sheet:

• for key exchange algorithms like Diffie-Hellman 👉 it's rte_crypto_asym_ke_type
• for ML-KEM algorithms 👉 it's rte_crypto_ml_kem_op_type
• for ML-DSA algorithms 👉 it's rte_crypto_ml_dsa_op_type
• for everything else 👉 it's rte_crypto_asym_op_type

Definition at line 167 of file rte_cryptodev.h.

---

🦋 struct rte_crypto_param_range modlen

Range of modulus length supported by modulus based xform. a value of 0 means the implementation default. (so like, "idk pick for me" but for math 🧮)

Definition at line 181 of file rte_cryptodev.h.

---

🍓 uint8_t internal_rng

Availability of random number generator for Elliptic curve based xform.

• value 0 means unavailable, and the application should pass the required random value itself 🙈
• otherwise, the PMD would internally compute the random number ✨

Definition at line 186 of file rte_cryptodev.h.

---

💜 uint32_t op_capa[RTE_CRYPTO_ASYM_OP_LIST_END]

Operation specific capabilities. 🛠️

Definition at line 192 of file rte_cryptodev.h.

---

🧚 uint32_t mlkem_capa[RTE_CRYPTO_ML_KEM_OP_END]

Bitmask of supported ML-KEM parameter sets. 🔐

Definition at line 195 of file rte_cryptodev.h.

---

⭐ uint32_t mldsa_capa[RTE_CRYPTO_ML_DSA_OP_END]

Bitmask of supported ML-DSA parameter sets. 🔏

Definition at line 198 of file rte_cryptodev.h.

---

🎀 uint64_t hash_algos

Bitmask of hash algorithms supported for op_type. 🧬

Definition at line 202 of file rte_cryptodev.h.

---

💖 Author 💖

Generated automatically by Doxygen for DPDK from the source code. (yes bestie, a robot wrote this and honestly? it ate. 🤖💅)

---

and that's the whole page!! mwah 💋 this was DPDK Version 25.11.3 of rte_crypto..._capability(3), so if you're reading this from a different version, go check your own build before you @ me. stay slaying, stay compiling, and remember: read the bitmask, respect the bitmask. 👑✨