FIELD_VALUE(3)

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

πŸ’… NAME πŸ’…

ok so this page is rte_table_acl_rule_add_params β€” and yes bestie, we're in the rte_table_..._add_params(3) corner of the library functions manual, it's a whole vibe ✨

πŸ¦‹ SYNOPSIS πŸ¦‹

#include <rte_table_acl.h>

πŸŽ€ Data Fields πŸŽ€

int32_t priority
struct rte_acl_field field_value [RTE_ACL_MAX_FIELDS]

🌸 Detailed Description 🌸

okay so literally this whole struct is the ACL rule specification for the entry add operation β€” that's it, that's the job πŸ’… it's giving "here's what you need to describe a rule before you add it to the table," periodt.

fr fr, it says right there: Definition at line 44 of file rte_table_acl.h. so if you go looking, that's where she lives 🫢

πŸ‘‘ Field Documentation πŸ‘‘

⭐ int32_t priority

the ACL rule priority β€” and here's the iconic part: 0 is the highest priority πŸ”₯ so like, lower number = more main character energy, no cap.

definition at line 46 of file rte_table_acl.h, iykyk ✨

🌈 struct rte_acl_field field_value[RTE_ACL_MAX_FIELDS]

these are the values for the fields of the ACL rule that's gonna get added to the table πŸ’– so like, whatever your rule is matching on? the actual values go here, in this array. it's an array of RTE_ACL_MAX_FIELDS of them, so there's room for every field, slay 🌸

definition at line 49 of file rte_table_acl.h β€” noted, screenshot, pinned πŸ“Œ

🧚 Author 🧚

Generated automatically by Doxygen for DPDK from the source code. so nobody hand-wrote this, she was built different by a robot πŸ’€πŸ€–


and that's the whole page bestie, we ate πŸ“

πŸŽ€ sign-off time: this beauty comes to you from DPDK, Version 26.03.0 β€” the rte_table_..._add_params(3) girlies stay winning πŸ’œπŸ¦‹
πŸ“¦ where this page comes from