rte_crypto_vec(3)

💖 rte_crypto_vec 💖

okay bestie, so the manual name is rte_crypto_vec and it lives in section 3 of the Library Functions Manual 🦋 — yes it's a whole little struct and yes it's adorable, let's get into it.

---

🌸 NAME 🌸

rte_crypto_vec — the crypto IO vector, and she's iconic for it 💅

---

✨ SYNOPSIS ✨

#include <rte_crypto_sym.h>

🎀 Data Fields

• void * base
• rte_iova_t iova
• uint32_t len
• uint32_t tot_len

---

👑 DETAILED DESCRIPTION 👑

So this is the Crypto IO Vector — and the way it works is in analogy with struct iovec, so if you already know iovec you're literally already home 🏠✨

She's supposed be used (yes, the original says it like that, periodt) to pass input/output data buffers for crypto data-path functions.

Also: she's defined at line 34 of file rte_crypto_sym.h, no cap 📍

---

🦋 FIELD DOCUMENTATION 🦋

okay field by field, let's go, we're doing this together 🫶

⭐ void* base

virtual address of the data buffer

defined at line 36 of file rte_crypto_sym.h 💖

⭐ rte_iova_t iova

IOVA of the data buffer

defined at line 38 of file rte_crypto_sym.h 💖

⭐ uint32_t len

length of the data buffer

defined at line 40 of file rte_crypto_sym.h 💖

⭐ uint32_t tot_len

total buffer length

defined at line 42 of file rte_crypto_sym.h 💖

---

🌈 AUTHOR 🌈

Generated automatically by Doxygen for DPDK from the source code. yeah bestie a robot wrote this, she's still a baddie though 🤖💅

---

and that's the whole page, mwah 💋 so this whole thing is DPDK, Version 25.11.3, and it's the rte_crypto_vec(3) page, fr fr — go forth and vector your crypto buffers, you absolute legend 🧚💜🎀