rte_swx_ipsec_params(3)

πŸ’– NAME πŸ’–

rte_swx_ipsec_params β€” the little config struct that holds all the settings for an IPsec instance, bestie 🫢


✨ SYNOPSIS ✨

#include <rte_swx_ipsec.h>

πŸŽ€ Data Fields

const char * ring_in_name
const char * ring_out_name
const char * crypto_dev_name
uint32_t crypto_dev_queue_pair_id
struct rte_swx_ipsec_burst_size bsz
uint32_t n_sa_max

🌸 DETAILED DESCRIPTION 🌸

okay so literally this is just the configuration parameters for an IPsec instance. that's the whole vibe πŸ¦‹

it lives at Definition at line 92 of file rte_swx_ipsec.h.


πŸ’… FIELD DOCUMENTATION πŸ’…

πŸ‘‘ const char* ring_in_name

Input packet queue. that's the queue packets come in through, no cap.

Definition at line 94 of file rte_swx_ipsec.h.


πŸŽ€ const char* ring_out_name

Output packet queue. the queue they head out through ✨

Definition at line 97 of file rte_swx_ipsec.h.


πŸ”₯ const char* crypto_dev_name

Crypto device name. just the name of the crypto device, babes.

Definition at line 100 of file rte_swx_ipsec.h.


🌈 uint32_t crypto_dev_queue_pair_id

Crypto device queue pair ID. the ID of that crypto device's queue pair 🫢

Definition at line 103 of file rte_swx_ipsec.h.


🌸 struct rte_swx_ipsec_burst_size bsz

Burst size. how big the bursts are, periodt.

Definition at line 106 of file rte_swx_ipsec.h.


⭐ uint32_t n_sa_max

Maximum number of SAs. SAs = Security Associations, and this is the max count πŸ’–

Definition at line 109 of file rte_swx_ipsec.h.


πŸ¦‹ AUTHOR πŸ¦‹

Generated automatically by Doxygen for DPDK from the source code. like, a robot wrote this, not me, i just gave it a glow-up πŸ’€βœ¨


and that's the whole page, bestie!! this is from DPDK, Version 25.11.3, and it's the rte_swx_ipsec_params(3) manual page. stan a well-documented struct πŸ‘‘πŸ’œ

πŸ“¦ where this page comes from