DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: skori@marvell.com, Xiaoyun Li <xiaoyun.li@intel.com>,
	Aman Singh <aman.deep.singh@intel.com>,
	Yuying Zhang <yuying.zhang@intel.com>,
	Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v4 1/1] app/testpmd: support different input color method
Date: Thu, 23 Jun 2022 14:05:45 +0300	[thread overview]
Message-ID: <db849204-446c-2435-f56b-510431f17aca@oktetlabs.ru> (raw)
In-Reply-To: <20220614100518.533931-1-skori@marvell.com>

On 6/14/22 13:05, skori@marvell.com wrote:
> From: Sunil Kumar Kori <skori@marvell.com>
> 
> To enable input coloring, based on VLAN or DSCP, patch adds
> command line interface to configure the following:
> 
>   - configuring input coloring using VLAN or DSCP while creating
>     meter i.e. during rte_mtr_create()
> 
>   - Update VLAN input coloring table at runtime.
> 
>   - configures protocol priorities.
> 
>   - retrieve protocol and priority information
> 
> Depends-on: patch-22751 ("ethdev: mtr: support protocol based input color selection")
> 
> Signed-off-by: Sunil Kumar Kori <skori@marvell.com>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> ---
> v3..v4:
>   - Replace strcmp with strcasecmp whereever is needed.
>   
> v2..v3:
>   - Rebased to branch ToT dpdk-next-net/main
>   - Fix static keyword for newly added token parsing symbols
> 
> v1..v2:
>   - Rebased to branch dpdk-next-net
>   - add CLIs for input coloring mechanism
> 
>   app/test-pmd/cmdline.c     |   4 +
>   app/test-pmd/cmdline_mtr.c | 552 ++++++++++++++++++++++++++++++++++++-
>   app/test-pmd/cmdline_mtr.h |   4 +
>   3 files changed, 554 insertions(+), 6 deletions(-)


doc/guides/testpmd_app_ug/testpmd_funcs.rst update is missing.
Please, respin it quickly and I'll process it today.

  reply	other threads:[~2022-06-23 11:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01  9:00 [PATCH v1 1/3] common/cnxk: update precolor table setup for VLAN skori
2022-03-01  9:00 ` [PATCH v1 2/3] net/cnxk: support ops to update precolor VLAN table skori
2022-06-16  9:48   ` [PATCH v2 1/2] common/cnxk: update precolor table setup for VLAN skori
2022-06-16  9:48     ` [PATCH v2 2/2] net/cnxk: support ops to update precolor VLAN table skori
2022-06-16 11:54       ` [PATCH v3 1/2] common/cnxk: update precolor table setup for VLAN skori
2022-06-16 11:54         ` [PATCH v3 2/2] net/cnxk: support ops to update precolor VLAN table skori
2022-06-20 17:44           ` Jerin Jacob
2022-06-21  7:19             ` [EXT] " Sunil Kumar Kori
2022-06-21  7:35           ` [PATCH v4 1/2] common/cnxk: update precolor table setup for VLAN skori
2022-06-21  7:35             ` [PATCH v4 2/2] net/cnxk: support ops to update precolor VLAN table skori
2022-08-22 12:33               ` Jerin Jacob
2022-03-01  9:00 ` [PATCH v1 3/3] app/testpmd: support different input color method skori
2022-05-20 22:09   ` Ferruh Yigit
2022-05-21  7:07     ` [EXT] " Sunil Kumar Kori
2022-05-23  8:43       ` Ferruh Yigit
2022-05-24  7:35   ` [PATCH v2 1/1] " skori
2022-05-25 12:36     ` Dumitrescu, Cristian
2022-05-25 14:32       ` Sunil Kumar Kori
2022-05-25 14:37     ` skori
2022-05-25 14:41       ` Dumitrescu, Cristian
2022-05-31 15:41         ` Andrew Rybchenko
2022-06-03 13:03           ` [EXT] " Sunil Kumar Kori
2022-06-03 13:06       ` [PATCH v3 " skori
2022-06-08 12:06         ` Andrew Rybchenko
2022-06-14 10:05         ` [PATCH v4 " skori
2022-06-23 11:05           ` Andrew Rybchenko [this message]
2022-06-23 12:54             ` [EXT] " Sunil Kumar Kori
2022-06-23 12:57           ` [PATCH v5 " skori
2022-06-23 13:07             ` Sunil Kumar Kori
2022-06-24 12:44             ` Andrew Rybchenko

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=db849204-446c-2435-f56b-510431f17aca@oktetlabs.ru \
    --to=andrew.rybchenko@oktetlabs.ru \
    --cc=aman.deep.singh@intel.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=skori@marvell.com \
    --cc=xiaoyun.li@intel.com \
    --cc=yuying.zhang@intel.com \
    /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).