From: Sunil Kumar Kori <skori@marvell.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"Li, Xiaoyun" <xiaoyun.li@intel.com>,
"Singh, Aman Deep" <aman.deep.singh@intel.com>,
"Zhang, Yuying" <yuying.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXT] Re: [PATCH v2 1/1] app/testpmd: support different input color method
Date: Fri, 3 Jun 2022 13:03:08 +0000 [thread overview]
Message-ID: <CO6PR18MB38608C12FD31B4D902EC99A6B4A19@CO6PR18MB3860.namprd18.prod.outlook.com> (raw)
In-Reply-To: <8cc3a0f3-e450-e3b9-b837-7c5bc8a738b5@oktetlabs.ru>
> -----Original Message-----
> From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
> Sent: Tuesday, May 31, 2022 9:12 PM
> To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Sunil Kumar Kori
> <skori@marvell.com>; Li, Xiaoyun <xiaoyun.li@intel.com>; Singh, Aman
> Deep <aman.deep.singh@intel.com>; Zhang, Yuying
> <yuying.zhang@intel.com>
> Cc: dev@dpdk.org
> Subject: [EXT] Re: [PATCH v2 1/1] app/testpmd: support different input color
> method
>
> External Email
>
> ----------------------------------------------------------------------
> On 5/25/22 17:41, Dumitrescu, Cristian wrote:
> >
> >
> >> -----Original Message-----
> >> From: skori@marvell.com <skori@marvell.com>
> >> Sent: Wednesday, May 25, 2022 3:37 PM
> >> To: Li, Xiaoyun <xiaoyun.li@intel.com>; Singh, Aman Deep
> >> <aman.deep.singh@intel.com>; Zhang, Yuying
> <yuying.zhang@intel.com>;
> >> Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> >> Cc: dev@dpdk.org; Sunil Kumar Kori <skori@marvell.com>
> >> Subject: [PATCH v2 1/1] app/testpmd: support different input color
> >> method
> >>
> >> 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>
> >> ---
> >> 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 | 558
> >> ++++++++++++++++++++++++++++++++++++-
> >
> > Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> >
>
> The patch breaks build as reported by CI [1].
> Please, fix and send v4 (since since one should be v3 in fact).
>
> [1]
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__patches.dpdk.org_project_dpdk_patch_20220525143716.996398-2D1-
> 2Dskori-
> 40marvell.com_&d=DwICaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=dXeXaAMkP5
> COgn1zxHMyaF1_d9IIuq6vHQO6NrIPjaE&m=lkdKT4ugU3ZTqTy2ee3r4GXH3m
> UCXIAOjWy80VtchoG__s3ty0EDuqXy3jL5y-
> 48&s=XHgyW7qwxFzk4FTe3Ul3gGCFbvRDegKDCAcqr1sAe1g&e=
>
> Note that you need to rebase on top of dpdk-next-net/main since nearby
> lines change due to static keyword addition. Don't forget to add to newly
> added cmdline_parse_* structs which are used in the file only.
Sure, I will rebase the changes on dpdk-next-net/main after fixing static keyword for
cmdline_parse_*.
Based on build error logs, I am suspecting that source is being compile against the dpdk/main.
next prev parent reply other threads:[~2022-06-03 13:03 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 ` Sunil Kumar Kori [this message]
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
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=CO6PR18MB38608C12FD31B4D902EC99A6B4A19@CO6PR18MB3860.namprd18.prod.outlook.com \
--to=skori@marvell.com \
--cc=aman.deep.singh@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--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).