The sched library checks the subport tc ov weight value regardless of whether RTE_SCHED_SUBPORT_TC_OV flag is enabled or not.
This fix allows application to always set valid tc ov weight value. Fixes: 25961ff3bcb9 ("examples/ip_pipeline: add traffic manager object") error log SCHED: pipe_profile_check: Incorrect value for tc ov weight SCHED: rte_sched_port_check_params: Pipe profile check failed(-22) Command "tmgr" failed. Signed-off-by: Jasvinder Singh <jasvinder.si...@intel.com> Acked-by: Cristian Dumitrescu <cristian.dumitre...@intel.com> --- v2: - add fix line - change title examples/ip_pipeline/cli.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/examples/ip_pipeline/cli.c b/examples/ip_pipeline/cli.c index f4c2be8b8..c6cf4204e 100644 --- a/examples/ip_pipeline/cli.c +++ b/examples/ip_pipeline/cli.c @@ -469,12 +469,10 @@ cmd_tmgr_pipe_profile(char **tokens, return; } -#ifdef RTE_SCHED_SUBPORT_TC_OV if (parser_read_uint8(&p.tc_ov_weight, tokens[19]) != 0) { snprintf(out, out_size, MSG_ARG_INVALID, "tc_ov_weight"); return; } -#endif for (i = 0; i < RTE_SCHED_BE_QUEUES_PER_PIPE; i++) if (parser_read_uint8(&p.wrr_weights[i], tokens[20 + i]) != 0) { -- 2.21.0