DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: "skori@marvell.com" <skori@marvell.com>,
	"Singh, Aman Deep" <aman.deep.singh@intel.com>,
	"Zhang, Yuying" <yuying.zhang@intel.com>,
	Nithin Dabilpuram <ndabilpuram@marvell.com>,
	Kiran Kumar K <kirankumark@marvell.com>,
	Satha Rao <skoteshwar@marvell.com>,
	"Singh, Jasvinder" <jasvinder.singh@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Ferruh Yigit <ferruh.yigit@xilinx.com>,
	"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v2 1/1] ethdev: add protocol param to color table update
Date: Tue, 23 Aug 2022 13:34:09 +0000	[thread overview]
Message-ID: <CH0PR11MB5724195F0C4F063F71DD76E3EB709@CH0PR11MB5724.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220823102255.2905191-1-skori@marvell.com>



> -----Original Message-----
> From: skori@marvell.com <skori@marvell.com>
> Sent: Tuesday, August 23, 2022 11:23 AM
> To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Singh, Aman Deep
> <aman.deep.singh@intel.com>; Zhang, Yuying <yuying.zhang@intel.com>;
> Nithin Dabilpuram <ndabilpuram@marvell.com>; Kiran Kumar K
> <kirankumark@marvell.com>; Sunil Kumar Kori <skori@marvell.com>; Satha
> Rao <skoteshwar@marvell.com>; Singh, Jasvinder
> <jasvinder.singh@intel.com>; Thomas Monjalon <thomas@monjalon.net>;
> Ferruh Yigit <ferruh.yigit@xilinx.com>; Andrew Rybchenko
> <andrew.rybchenko@oktetlabs.ru>
> Cc: dev@dpdk.org
> Subject: [PATCH v2 1/1] ethdev: add protocol param to color table update
> 
> From: Sunil Kumar Kori <skori@marvell.com>
> 
> Using rte_mtr_color_in_protocol_set(), user can configure
> combination of protocol headers, like outer_vlan and outer_ip,
> can be enabled on given meter object.
> 
> But rte_mtr_meter_vlan_table_update() and
> rte_mtr_meter_dscp_table_update() do not have information that
> which table needs to be updated corresponding to protocol header
> i.e. inner or outer.
> 
> Adding protocol paramreter will allow user to provide required
> protocol information so that corresponding inner or outer table
> can be updated corresponding to protocol header.
> 
> If user wishes to configure both inner and outer table then
> API must be called twice with correct protocol information.
> 
> Signed-off-by: Sunil Kumar Kori <skori@marvell.com>
> ---
> v1..v2:
>  - Rebase on ToT of dpdk-next-net-mrvl/for-next-net branch.
>  - Remove "Depends On:" tag as dependent patch is merged.
> 

Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>


  reply	other threads:[~2022-08-23 13:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07  6:57 [PATCH] " skori
2022-07-21  7:32 ` Sunil Kumar Kori
2022-08-16  5:56   ` Sunil Kumar Kori
2022-08-23 10:22 ` [PATCH v2 1/1] " skori
2022-08-23 13:34   ` Dumitrescu, Cristian [this message]
2022-10-03 14:42     ` Ferruh Yigit

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=CH0PR11MB5724195F0C4F063F71DD76E3EB709@CH0PR11MB5724.namprd11.prod.outlook.com \
    --to=cristian.dumitrescu@intel.com \
    --cc=aman.deep.singh@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@xilinx.com \
    --cc=jasvinder.singh@intel.com \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@marvell.com \
    --cc=thomas@monjalon.net \
    --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).