RING_RD(3)

πŸ“¦ version 26.03, in nixos 26.05, nixpkgs unstable

πŸ’… NAME πŸ’…

rte_swx_ipsec_burst_size β€” bestie, this is the struct that holds all the IPsec burst sizes, like, every single one of them ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

#include <rte_swx_ipsec.h>

πŸŽ€ Data Fields πŸŽ€

  • uint32_t ring_rd
  • uint32_t ring_wr
  • uint32_t crypto_wr
  • uint32_t crypto_rd

πŸ”₯ Detailed Description πŸ”₯

Okay so picture this: it's the IPsec burst sizes struct, and it's literally just here to hold four numbers, no cap. That's the whole vibe. πŸ’…

Definition at line 75 of file rte_swx_ipsec.h.

🌸 Field Documentation 🌸

πŸ’– uint32_t ring_rd πŸ’–

The burst size for reading from the input ring. The way that this one is all about how much you pull in at once 🫢

Definition at line 77 of file rte_swx_ipsec.h.

🌈 uint32_t ring_wr 🌈

The burst size for writing to the output ring. Same energy as ring_rd but it's giving output, main character outgoing vibes ⭐

Definition at line 80 of file rte_swx_ipsec.h.

🧚 uint32_t crypto_wr 🧚

The burst size for writing to the crypto device request queue. Like, how many requests you yeet at the crypto device in one go πŸ”₯

Definition at line 83 of file rte_swx_ipsec.h.

πŸ“ uint32_t crypto_rd πŸ“

The burst size for reading from the crypto device response queue. How many answers you scoop up per round, lowkey essential πŸ™ˆ

Definition at line 86 of file rte_swx_ipsec.h.

πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code. Not me writing this by hand, bestie β€” the tooling did it πŸ’€


and that's the whole page, periodt πŸ’œ this was DPDK, Version 26.03.0, page rte_swx_ipsec_burst_size(3) β€” slay, go read the header for the real tea πŸŽ€βœ¨

πŸ“¦ where this page comes from