rte_pmd_cn...ec_outb_iv(3)
β¨ NAME β¨
rte_pmd_cnxk_ipsec_outb_iv β bestie, this is a struct that holds outbound IPsec IV data π (and yeah, the page header up top squishes the name down to rte_pmd_cn...ec_outb_iv(3) because terminal width said no π β it's the Library Functions Manual, section 3, iykyk).
πΈ SYNOPSIS πΈ
#include <rte_pmd_cnxk.h>
π Data Fields π
uint8_t iv_dbg [16]
π¦ Detailed Description π¦
Okay so this whole struct is literally just Outbound IPsec IV data π. That's the vibe. That's the assignment.
Heads up bestie: it says the definition lives at line 134 of the file rte_pmd_cnxk.h β noted, cited, slayed β¨
π Field Documentation π
So the fields are where it gets a lil' quirky β the SYNOPSIS only shows you one field, but the docs are gonna drop four on you. Not a drill, not a typo on my end, I'm giving you exactly what the page gives π
uint8_t iv_dbg[16]β the IV debug field, 16B π«Ά. Defined at line 137 ofrte_pmd_cnxk.h.uint8_t iv_dbg1[4]β IV debug, 8B. Yes bestie, the array says[4]and the description says 8B β that's what the page says, so that's what I'm telling you, no editing, no cap π. Defined at line 140 ofrte_pmd_cnxk.h.uint8_t salt[4]β the Salt π§β¨. Defined at line 142 ofrte_pmd_cnxk.h.uint8_t iv_dbg2[4]β IV debug, 8B (again with the[4]vs 8B situation, and again I'm just the messenger π). Defined at line 146 ofrte_pmd_cnxk.h.
Fr fr, the 4-vs-8B thing is exactly how the page describes it β I'm not out here inventing lore π
π Author π
Generated automatically by Doxygen for DPDK from the source code. So nobody hand-wrote this, it's a whole robot doing the typing, and honestly? It ate π€π
And that's the whole page, bestie β sign-off time: this gorgeous little artifact comes to you from DPDK, Version 26.03.0. Go forth and IV responsibly π¦π
π¦ where this page comes from
- nixos 26.05: dpdk 26.03
- nixpkgs unstable: dpdk 26.03
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms