RTE_TABLE_ACL_RULE_ADD_PARAMS(3)
β¨ NAME β¨
rte_table_acl_rule_add_params β bestie, this is the little struct that holds the spec for adding an ACL rule to your table π
(also hi, this is from the Library Functions Manual, if you were wondering what kind of manual you wandered into π)
πΈ 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, no cap: this is the ACL rule specification for the entry add operation. That's the whole vibe. It's the little bundle of info you hand over when you want a new rule shoved into the table β¨
π
Fun fact for the lore girlies: the definition lives at line 44 of the file rte_table_acl.h. Iconic placement, honestly.
π FIELD DOCUMENTATION π
π int32_t priority
This is the ACL rule priority, and listen β 0 is the highest priority. Zero. The smallest number. The main character. Priority is literally giving "lower number = more important," so don't let the ranking fool you bestie π
π Defined at line 46 of rte_table_acl.h.
π struct rte_acl_field field_value[RTE_ACL_MAX_FIELDS]
These are the values for the fields of the ACL rule that's about to be added to the table. So it's an array of struct rte_acl_field and it holds up to RTE_ACL_MAX_FIELDS of them. The math is mathing, the fields are fielding π§
π Defined at line 49 of rte_table_acl.h.
π AUTHOR π
Generated automatically by Doxygen for DPDK, straight from the source code. Not me writing fanfic, that's just how it's made π«Ά
And that's the whole page, bestie! This one came from DPDK, Version 25.11.3 β go forth, add your rules, and slay πβ¨π (also congrats on reading the whole thing, that's the vibe check passed fr fr πΈ)
π¦ where this page comes from
- ubuntu resolute: dpdk-doc 25.11.3-0ubuntu0.26.04.1 Β· BSD-3-Clause
- ubuntu stonking: dpdk-doc 25.11.3-1 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms