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