rte_table_...pto_config(3)

πŸ’– NAME πŸ’–

rte_table_action_sym_crypto_config β€” bestie, this is the symmetric crypto action configuration struct, and it's a per table action profile kinda deal πŸ’…

Manual section 3, Library Functions Manual energy. Yes we're in the library pages, and yes we're thriving ✨


🌸 SYNOPSIS 🌸

#include <rte_table_action.h>

πŸŽ€ Data Fields

  • uint8_t cryptodev_id
  • uint32_t op_offset
  • struct rte_mempool * mp_create
  • struct rte_mempool * mp_init

✨ DETAILED DESCRIPTION ✨

Symmetric crypto action configuration, and it's per table action profile β€” like, every action profile gets to have its own lil crypto setup. Obsessed 🫢

Defined at line 729 of the file rte_table_action.h. Iconic placement, no notes.


πŸ¦‹ FIELD DOCUMENTATION πŸ¦‹

uint8_t cryptodev_id

The target Cryptodev ID. That's the one you're pointing at, bestie β€” the Cryptodev you wanna target 🎯

Defined at line 731 of the file rte_table_action.h.


uint32_t op_offset

Offset to the rte_crypto_op structure within the input packet buffer. And listen β€” offset 0 points to the first byte of the MBUF structure. Zero means the very top of the MBUF, not "wherever feels right" 😭

Defined at line 737 of the file rte_table_action.h.


struct rte_mempool* mp_create

The mempool for creating cryptodev sessions. It's the creation mempool, she makes the sessions πŸ’–

Defined at line 740 of the file rte_table_action.h.


struct rte_mempool* mp_init

The mempool for initializing cryptodev sessions. Separate pool, separate job, we don't conflate them ✨

Defined at line 743 of the file rte_table_action.h.


πŸ‘‘ AUTHOR πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code. So like, nobody wrote this by hand, the robot did it, and honestly? It ate πŸ™ˆ


No cap: every single line above was auto-generated from the source, so if you're about to yell at a human maintainer about the wording β€” it was Doxygen. Blame the robot 🫢

That's the whole page, bestie β€” DPDK, Version 25.11.3, and this beauty is dated right there in the rte_table_...pto_config(3) footer. Slay, go write some crypto actions πŸ’…πŸ’–

πŸ“¦ where this page comes from