RTE_CRYPTO_ML_DSA_KEYGEN_OP(3)

💖 NAME 💖

rte_crypto_ml_dsa_keygen_op — bestie, this is the struct that holds everything the DPDK crypto stack needs to do an ML-DSA keygen. That's post-quantum, babe. Yes, the quantum-resistant kind. 🔥

---

✨ SYNOPSIS ✨

#include <rte_crypto_asym.h>

🎀 Data Fields 🎀

• rte_crypto_param seed
• rte_crypto_param pubkey
• rte_crypto_param privkey

---

🌸 DETAILED DESCRIPTION 🌸

okay so. PQC ML-DSA KEYGEN op. 🫶

This is where you drop the parameters for a PQC ML-DSA key generation operation. It's literally just the little bundle of params that tells the keygen what to work with and where to put the results.

Definition at line 961 of file rte_crypto_asym.h. (yes, we cite line numbers here, we're nothing if not thorough 💅)

---

🦋 FIELD DOCUMENTATION 🦋

rte_crypto_param seed

The random seed — and it has to be 32 bytes in length — that generates the key pair. No seed, no keys, no vibes. 🌱

Definition at line 962 of file rte_crypto_asym.h.

rte_crypto_param pubkey

Pointer to output data, bestie. This is where the good stuff lands:

• The computed public key. 👑
• Refer rte_crypto_ml_dsa_pubkey_size for size of buffer. Do not skip this, seriously, that's your buffer sizing right there.

Definition at line 965 of file rte_crypto_asym.h.

rte_crypto_param privkey

Pointer to output data, again. Your secret little main character:

• The computed secret key. 🙈
• Refer rte_crypto_ml_dsa_privkey_size for size of buffer. Same energy — that function is how you know how much room to give it.

Definition at line 972 of file rte_crypto_asym.h.

---

👑 AUTHOR 👑

Generated automatically by Doxygen for DPDK from the source code. Not a human, not a friend, just a doc generator doing its absolute most. 😭

---

and that's the whole page, periodt. credit where it's due: this came out of DPDK, Version 25.11.3, with the rte_crypto...a_keygen_op(3) header on it — mwah, go read some source code, ily 🎀🦋💜