rte_crypto_param_range(3)

✨ rte_crypto_param_range ✨ (that's a section 3 manpage, bestie — Library Functions Manual energy 🫶)

💖 NAME 💖

rte_crypto_param_range — no cap, that's literally the whole name, it's a struct and it's here to tell you what sizes a crypto thing can be 💅

---

🌸 SYNOPSIS 🌸

#include <rte_cryptodev.h>

🎀 Data Fields

• uint16_t min
• uint16_t max
• uint16_t increment

---

🦋 DETAILED DESCRIPTION 🦋

It's a crypto parameters range description — like, the vibe is "here's the window of sizes you're allowed to play in" 📏✨

Defined at line 84 of the file rte_cryptodev.h. iykyk.

---

💜 FIELD DOCUMENTATION 💜

⭐ uint16_t min

The minimum size. The floor. The bare minimum. She will not go lower 🙅‍♀️

Defined at line 85 of the file rte_cryptodev.h.

🌈 uint16_t max

The maximum size. The ceiling. The limit. Dream big but not that big 💭

Defined at line 86 of the file rte_cryptodev.h.

💅 uint16_t increment

The moment we've all been waiting for 👑 If a range of sizes is supported — and yes bestie, that's an if — then this parameter is what tells you the increments in byte size that are supported between the minimum and the maximum. So like, you don't get every single size in between, you get the ones that land on this step 🪜✨

Defined at line 87 of the file rte_cryptodev.h.

---

🌟 AUTHOR 🌟

Generated automatically by Doxygen for DPDK from the source code. So nobody hand-wrote this one, the robot did it, and honestly? She ate 🤖💖

---

Ok that's the whole page, bestie! This one came out of the DPDK gang, specifically Version 25.11.3. Go forth and respect the increment, periodt 🎀🦋💅