RTE_MTR_METER_POLICY_PARAMS(3)
π rte_mtr_meter_policy_params(3) π
okay bestie, so this is a page from the Library Functions Manual for rte_mtr_meter_policy_params β yes it's a mouthful, yes it's iconic, let's go π«Ά
β¨ NAME β¨
rte_mtr_meter_policy_params β the whole vibe check for your meter policy, no cap π
πΈ SYNOPSIS πΈ
#include <rte_mtr.h>
π Data Fields
const struct rte_flow_action * actions [RTE_COLORS]
π¦ Detailed Description π¦
Bestie. It's giving Meter policy. That's literally it, that's the whole thing. π
Definition at line 205 of file rte_mtr.h.
β Field Documentation β
π const struct rte_flow_action* actions[RTE_COLORS]
So this one is the policy action list per color. Think of it like, one action list for each color, and actions[i] is doing the absolute most, because it potentially represents a chain of rte_flow actions terminated by the END action β exactly as specified by the rte_flow API for the flow definition β and not just a single action. Like, it's a whole group chat of actions in there, not one lonely message, iykyk π₯
Definition at line 212 of file rte_mtr.h.
π Author π
Generated automatically by Doxygen for DPDK from the source code. Not me writing it by hand, not you writing it by hand β the machine did that, and honestly? It ate. π€β¨
that's the whole page bestie, we're done here π stay hydrated, read your struct definitions, and remember: this was DPDK, Version 25.11.3, from the rte_mtr_me...licy_params(3) manual β periodt ππ
π¦ 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