From: "Singh, Jasvinder" <jasvinder.singh@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] examples/ip_pipeline: remove tc ov flag from pipe profile cli
Date: Tue, 6 Aug 2019 11:50:22 +0000 [thread overview]
Message-ID: <54CBAA185211B4429112C315DA58FF6D3FDB0C6C@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <2346997.vLtd3DEVLB@xps>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Tuesday, August 6, 2019 11:43 AM
> To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Singh, Jasvinder
> <jasvinder.singh@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] examples/ip_pipeline: remove tc ov flag from
> pipe profile cli
>
> 31/07/2019 14:19, Dumitrescu, Cristian:
> > From: Singh, Jasvinder
> > > Subject: [PATCH] examples/ip_pipeline: remove tc ov flag from pipe
> > > profile cli
> > >
> > > Since sched library always check the non-zero value of subport tc ov
> > > weight. Therefore, it is necessary to set right value of tc ov
> > > weight even if RTE_SCHED_SUBPORT_TC_OV is disabled.
>
> If I understand well, this is fixing something, but what?
> Please could you propose a better title and a "Fixes" line?
> Thanks
>
Sent v2 version. Thank you.
next prev parent reply other threads:[~2019-08-06 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 11:33 Jasvinder Singh
2019-07-31 12:19 ` Dumitrescu, Cristian
2019-08-06 10:42 ` Thomas Monjalon
2019-08-06 11:50 ` Singh, Jasvinder [this message]
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
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=54CBAA185211B4429112C315DA58FF6D3FDB0C6C@IRSMSX103.ger.corp.intel.com \
--to=jasvinder.singh@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).