rte_tm_wred_params(3)
π rte_tm_wred_params π
okay bestie, gather round, because we're doing a struct today and honestly? it's giving congestion-management icon. this is from the DPDK library functions manual, and it's literally called rte_tm_wred_params. yes it comes from rte_tm.h, yes you're gonna need it if you're messing with traffic management, no you cannot skip it. let's go π¦
β¨ NAME β¨
rte_tm_wred_params β the struct that holds your Weighted RED (WRED) profile, periodt π
πΈ SYNOPSIS πΈ
#include <rte_tm.h>
π Data Fields
struct rte_tm_red_params red_params [RTE_COLORS]int packet_mode
π DESCRIPTION π
so this whole thing is the Weighted RED (WRED) profile, and here's the tea:
multiple WRED contexts can share the same WRED profile. no gatekeeping, they just share. π₯
every leaf node that has WRED enabled as its congestion management mode has zero or one private WRED context (aka only one leaf node using it) and/or zero, one or several shared WRED contexts (aka multiple leaf nodes use the same WRED context).
- a private WRED context does congestion management for a single leaf node, just the one, main character behavior honestly
- a shared WRED context does congestion management for a whole group of leaf nodes, very group-chat of it π«Ά
π§ See also
struct rte_tm_capabilities::cman_wred_packet_mode_supportedstruct rte_tm_capabilities::cman_wred_byte_mode_supported
lowkey important note: this is defined at line 994 of file rte_tm.h. remember that, it might come up. β¨
π FIELD DOCUMENTATION π
π struct rte_tm_red_params red_params[RTE_COLORS]
one set of RED parameters per packet color. that's it, that's the whole vibe β one per color. π¨
defined at line 996 of file rte_tm.h
β int packet_mode
okay so this one is a little switch and it changes everything about how your thresholds are counted, so pay attention bestie π
- when
packet_modeis non-zero, themin_thandmax_ththresholds are specified in packets β that's WRED packet mode - when
packet_modeis zero, themin_thandmax_ththresholds are specified in bytes β that's WRED byte mode
no in-between, no "oh it's probably fine", it's literally just which unit your thresholds are living in. pick wisely. π
defined at line 1002 of file rte_tm.h
π¦ AUTHOR π¦
generated automatically by Doxygen for DPDK from the source code. yes, a robot wrote this, and the robot ate. π€β¨
alright that's the whole page, you're officially educated on rte_tm_wred_params and i'm so proud of you π this was DPDK, Version 25.11.3, and you read the whole thing which is honestly iconic of you. go forth and configure your thresholds correctly, bestie. not me being obsessed with a WRED profile. ππ
slay π
π¦ 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