Searched refs:RED (Results 1 – 9 of 9) sorted by relevance
| /dpdk/examples/qos_meter/ |
| H A D | main.h | 11 RED = RTE_COLOR_RED, enumerator 18 { GREEN, RED, RED}, 19 { DROP, YELLOW, RED}, 20 { DROP, DROP, RED}
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | qos_framework.rst | 1182 The purpose of the RED/PIE algorithm is to monitor a packet queue, 1194 different RED configurations for the same packet queue at run-time. 1200 The RED/WRED/PIE algorithm is exercised first and tail drop second. 1242 .. table:: RED Configuration Parameters 1263 corresponds to the format used by Cisco* in their RED implementation. 1509 Packet Drop Probability for a Given RED Configuration 1539 one that has been taken by other RED implementations, for example, FreeBSD* ALTQ RED. 1571 RED functionality in the DPDK QoS scheduler is disabled by default. 1582 The configuration file includes a section containing RED parameters. 1593 ; RED params per traffic class and color (Green / Yellow / Red) [all …]
|
| H A D | traffic_management.rst | 116 The Random Early Detection (RED) algorithm works by proactively dropping more 118 or almost full, RED effectively works as Tail Drop. The Weighted RED (WRED) 119 algorithm uses a separate set of RED thresholds for each packet color and uses 120 separate set of RED thresholds for each packet color.
|
| H A D | glossary.rst | 179 RED
|
| /dpdk/examples/qos_sched/ |
| H A D | profile_ov.cfg | 61 ; RED params per traffic class and color (Green / Yellow / Red)
|
| H A D | profile.cfg | 78 ; RED params per traffic class and color (Green / Yellow / Red)
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | qos_metering.rst | 123 * RED: The packet's color is changed to red.
|
| /dpdk/doc/api/ |
| H A D | doxy-api-index.md | 132 [RED congestion] (@ref rte_red.h)
|
| /dpdk/doc/guides/nics/ |
| H A D | mlx5.rst | 445 - RED: DROP / END. 449 - RED: must be DROP.
|