Z(3)

💖 NAME 💖

rte_crypto_ml_kem_keygen_op — okay bestie, this is the struct definition for a PQC ML-KEM KEYGEN op, straight out of DPDK's asymmetric crypto header 🎀✨

---

✨ SYNOPSIS ✨

#include <rte_crypto_asym.h>

🌸 Data Fields 🌸

• rte_crypto_param d
• rte_crypto_param z
• rte_crypto_param ek
• rte_crypto_param dk

---

🦋 DETAILED DESCRIPTION 🦋

So basically 💅: this is the PQC ML-KEM KEYGEN op — like, the whole vibe is parameters for the PQC ML-KEM key generation operation. That's the main character energy of this struct, no cap 🔥

Definition at line 813 of file rte_crypto_asym.h.

---

🎀 FIELD DOCUMENTATION 🎀

💜 rte_crypto_param d

The seed d value — and yes it's 32 bytes in length — used to generate the key pair 🌱

Definition at line 814 of file rte_crypto_asym.h.

💜 rte_crypto_param z

The seed z value, also 32 bytes in length (twins fr fr), used to generate the key pair 🦋

Definition at line 817 of file rte_crypto_asym.h.

💜 rte_crypto_param ek

Pointer to output data 👑

• The computed encapsulation key.
• Refer rte_crypto_ml_kem_pubkey_size for size of buffer. (iykyk — go check it before you allocate, bestie, seriously)

Definition at line 820 of file rte_crypto_asym.h.

💜 rte_crypto_param dk

Pointer to output data 🗝️

• The computed decapsulation key.
• Refer rte_crypto_ml_kem_privkey_size for size of buffer. (same deal — that's your size source of truth)

Definition at line 827 of file rte_crypto_asym.h.

---

🫶 AUTHOR 🫶

Generated automatically by Doxygen for DPDK from the source code. (not a human, just a little robot doing its thing 🤖✨)

---

Heads up bestie — a lot of these fields are pointers to output data, so make sure your buffers are actually sized right using rte_crypto_ml_kem_pubkey_size and rte_crypto_ml_kem_privkey_size before you go handing them over. That's a whole vibe check you don't wanna fail 😭

---

And that's the page! 🌈 Brought to you by DPDK, Version 26.03.0 — rte_crypto...m_keygen_op(3), mwah 💋 go forth and generate those keys, queen 👑