odp_tm_level_requirements_t Struct Reference

Per Level Requirements. More...

#include <traffic_mngr.h>

Data Fields
uint32_t	max_num_tm_nodes
	max_num_tm_nodes specifies the maximum number of tm_nodes required at this level.
uint32_t	max_fanin_per_node
	max_fanin_per_level specifies the maximum number of fan_in links to any given scheduler (whether weighted or using fair queueing or round robin) required of tm_nodes at this level.
uint8_t	max_priority
	max_priority specifies the maximum number of strict priority levels that will be used by any tm_node at this level. More...
uint32_t	min_weight
	min_weight only has significance when the weights_supported field below is true, in which case it specifies the smallest value of the weights that will be used at this level.
uint32_t	max_weight
	max_weight only has significance when the weights_supported field below is true, in which case it specifies the largest value of the weights that will be used at this level.
odp_bool_t	tm_node_shaper_needed
	tm_node_shaper_needed indicates that the tm_nodes at this level are expected to do TM shaping,
odp_bool_t	tm_node_wred_needed
	tm_node_wred_needed indicates that the tm_nodes at this level are expected to participate in some form of Random Early Detection.
odp_bool_t	tm_node_dual_slope_needed
	tm_node_dual_slope_needed indicates that the tm_nodes at this level are expected to use the dual slope WRED capability. More...
odp_bool_t	fair_queuing_needed
	fair_queuing_needed indicates that the tm_node schedulers at this level are expected to implement WFQ or FQ scheduling disciplines.
odp_bool_t	weights_needed
	weights_needed indicates that the tm_node schedulers at this level are expected have different weights for their different fanins. More...
odp_bool_t	tm_node_threshold_needed
	tm_node_threshold_needed indicates that the tm_nodes at this level may use threshold profile support

Detailed Description

Per Level Requirements.

The odp_tm_level_requirements_t record is used to describe the requirements that might vary based upon the tm_node level. It is always used as part of the odp_tm_requirements record. The default value of all boolean fields is false.

Examples

odp_traffic_mgmt.c.

Definition at line 573 of file api/spec/traffic_mngr.h.

Field Documentation

max_priority

uint8_t odp_tm_level_requirements_t::max_priority

max_priority specifies the maximum number of strict priority levels that will be used by any tm_node at this level.

Note that lower numeric values represent higher (more important or time critical) priorities.

Examples

odp_traffic_mgmt.c.

Definition at line 587 of file api/spec/traffic_mngr.h.

tm_node_dual_slope_needed

odp_bool_t odp_tm_level_requirements_t::tm_node_dual_slope_needed

tm_node_dual_slope_needed indicates that the tm_nodes at this level are expected to use the dual slope WRED capability.

This field is ignored if tm_node_wred_needed above is false.

Examples

odp_traffic_mgmt.c.

Definition at line 611 of file api/spec/traffic_mngr.h.

weights_needed

odp_bool_t odp_tm_level_requirements_t::weights_needed

weights_needed indicates that the tm_node schedulers at this level are expected have different weights for their different fanins.

When true the min_weight and max_weight fields above specify the used range of such weights.

Examples

odp_traffic_mgmt.c.

Definition at line 622 of file api/spec/traffic_mngr.h.

---

The documentation for this struct was generated from the following file:

• api/spec/traffic_mngr.h