rte_table_..._lb_config(3)

πŸ’– rte_table_..._lb_config(3) πŸ’–

okay bestie, welcome to the Library Functions Manual entry for rte_table_..._lb_config(3) β€” yes the title has dots in it, that's just how Doxygen does, we don't question it, we respect it πŸ’…


✨ NAME ✨

rte_table_action_lb_config β€” the load-ballance action config struct, and yes we're pronouncing it like that now πŸŽ€


🌸 SYNOPSIS 🌸

#include <rte_table_action.h>

πŸ¦‹ Data Fields πŸ¦‹

  • uint32_t key_size
  • uint32_t key_offset
  • uint8_t key_mask[RTE_TABLE_ACTION_LB_KEY_SIZE_MAX]
  • rte_table_hash_op_hash f_hash
  • uint64_t seed
  • uint32_t out_offset

πŸ’œ Detailed Description πŸ’œ

so this is the load balance action configuration β€” and it's per table action profile, meaning every action profile gets its own lil copy, no sharing, main character energy only πŸ‘‘

Definition at line 146 of file rte_table_action.h.

πŸ”₯ Field Documentation πŸ”₯

πŸ’« uint32_t key_size

key size, bestie β€” as in the number of bytes, that's the unit, don't come at me with bits πŸ“

Definition at line 148 of file rte_table_action.h.

πŸ’« uint32_t key_offset

where the key starts, as an offset within the input packet buffer. And listen β€” offset 0 points to the first byte of the MBUF structure, not the packet payload, not the headers, the MBUF itself. write that down. tattoo it. πŸ“

Definition at line 153 of file rte_table_action.h.

πŸ’« uint8_t key_mask[RTE_TABLE_ACTION_LB_KEY_SIZE_MAX]

the key mask, queen πŸ‘‘ and the important bit: only key_size bytes are valid. the rest of that array is just vibes, do not read it, do not trust it, look away πŸ™ˆ

Definition at line 156 of file rte_table_action.h.

πŸ’« rte_table_hash_op_hash f_hash

your hash function. literally just the function pointer, that's the whole tea β˜•

Definition at line 159 of file rte_table_action.h.

πŸ’« uint64_t seed

the seed value for f_hash. feed it to your hash function and let it cook πŸ”₯

Definition at line 162 of file rte_table_action.h.

πŸ’« uint32_t out_offset

where the output value goes β€” an offset within the input packet buffer. Same rules as before, no cap: offset 0 points to the first byte of the MBUF structure. it's giving symmetry, it's giving consistency 🌈

Definition at line 167 of file rte_table_action.h.

🌟 Author 🌟

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


and that's the whole page bestie, we did it, we read a struct together 🫢

this was DPDK, Version 25.11.3, manual section rte_table_..._lb_config(3) β€” go forth and load balance, ily, bye πŸ’–πŸ’…

πŸ“¦ where this page comes from