DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jasvinder Singh <jasvinder.singh@intel.com>
Cc: dev@dpdk.org, cristian.dumitrescu@intel.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] examples/ip_pipeline: fix wrong value of tc ov weight
Date: Tue, 06 Aug 2019 15:26:28 +0200	[thread overview]
Message-ID: <3667816.tTLe76bmax@xps> (raw)
In-Reply-To: <20190806114951.62131-1-jasvinder.singh@intel.com>

06/08/2019 13:49, Jasvinder Singh:
> 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.singh@intel.com>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> ---
> v2:
> - add fix line
> - change title

"tc ov" is not that obvious.
I changed the title to "examples/ip_pipeline: fix TC oversubscription weight"

+Add Cc stable

Applied, thanks



  reply	other threads:[~2019-08-06 13:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31 11:33 [dpdk-dev] [PATCH] examples/ip_pipeline: remove tc ov flag from pipe profile cli Jasvinder Singh
2019-07-31 12:19 ` Dumitrescu, Cristian
2019-08-06 10:42   ` Thomas Monjalon
2019-08-06 11:50     ` Singh, Jasvinder
2019-08-06 11:49 ` [dpdk-dev] [PATCH v2] examples/ip_pipeline: fix wrong value of tc ov weight Jasvinder Singh
2019-08-06 13:26   ` Thomas Monjalon [this message]
2019-09-04 17:26     ` Kevin Traynor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3667816.tTLe76bmax@xps \
    --to=thomas@monjalon.net \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=jasvinder.singh@intel.com \
    --cc=stable@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).