rte_crypto_sym_vec(3)

πŸ’– rte_crypto_sym_vec πŸ’–

okay bestie, welcome to the rte_crypto_sym_vec(3) page β€” section 3, Library Functions Manual, we're in DPDK land, and this lil struct is so much less scary than it looks, i promise 🫢


✨ NAME ✨

rte_crypto_sym_vec β€” the raw data operation descriptor struct, and like, it's kind of a whole vibe check for a batch of crypto ops πŸ‘‘


🌸 SYNOPSIS 🌸

#include <rte_crypto_sym.h>

πŸŽ€ Data Fields

  • uint32_t num
  • struct rte_crypto_sgl * src_sgl
  • struct rte_crypto_sgl * dest_sgl
  • struct rte_crypto_va_iova_ptr * iv
  • struct rte_crypto_va_iova_ptr * digest
  • int32_t * status

πŸ¦‹ Detailed Description πŸ¦‹

It's the Raw data operation descriptor, bestie. It's supposed to be used with the synchronous CPU crypto API call, or with the asynchronous RAW data path API call β€” those are literally its two whole purposes, it's giving very "i have one job and i slay at it" energy πŸ’…

ngl this struct has main character energy: it's defined at line 71 of the file rte_crypto_sym.h. remember that. it's in the lore. ✨

πŸ’œ Field Documentation πŸ’œ

🌈 uint32_t num

It's the number of operations to perform β€” like, how many things are we doing today, bestie? that many. πŸ“

Defined at line 73 of file rte_crypto_sym.h.


🌈 struct rte_crypto_sgl* src_sgl

An array of SGL vectors. yes queen, arrays. we love a list of them. πŸ’–

Defined at line 75 of file rte_crypto_sym.h.


🌈 struct rte_crypto_sgl* dest_sgl

An array of SGL vectors for OOP β€” and here's the important part, no cap: keep it NULL for inplace. like, do NOT fill this in if you're doing inplace, that's the whole rule, i don't make them i just report them πŸ™ˆ

Defined at line 77 of file rte_crypto_sym.h.


🌈 struct rte_crypto_va_iova_ptr* iv

An array of pointers to cipher IV</array>. iv as in initialization vector, not as in the roman numeral, stay focused bestie 😭

Defined at line 79 of file rte_crypto_sym.h.


🌈 struct rte_crypto_va_iova_ptr* digest

An array of pointers to digest. mmm digest. like the algorithm ate your data and this is the receipt πŸ’€

Defined at line 81 of file rte_crypto_sym.h.


🌈 struct rte_crypto_va_iova_ptr* auth_iv

An array of pointers to auth IV</array> β€” and this one is used for chain operation specifically. chain! not AEAD! keep them straight, i'm begging 🧚

Defined at line 86 of file rte_crypto_sym.h.


🌈 struct rte_crypto_va_iova_ptr* aad

An array of pointers to AAD</array> β€” that's Additional Authenticated Data, and it's used for AEAD operation. different field, different operation, don't mix them up or it's gonna be a bad time fr fr 🫢

Defined at line 88 of file rte_crypto_sym.h.


🌈 int32_t* status

An array of statuses for each operation, one per op, and the values are literally just:

  • 0 on success πŸŽ‰
  • errno on error 😭

so check your statuses. every single one. yes all of them. i said what i said. ⭐

Defined at line 96 of file rte_crypto_sym.h.


πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code. yes, a robot wrote it, and honestly? it ate. πŸ€–βœ¨


and that's the whole page bestie!! author-signed by doxygen, DPDK Version 25.11.3, page rte_crypto_sym_vec(3), mwah πŸ’‹ go forth and batch your crypto ops responsibly, love u, bye πŸ‘‘πŸ’–πŸŒ™

πŸ“¦ where this page comes from