DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Minggang(Gavin) Li" <gavinl@nvidia.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>,
	Matan Azrad <matan@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	Ori Kam <orika@nvidia.com>,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
	Aman Singh <aman.deep.singh@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Raslan Darawsheh <rasland@nvidia.com>
Subject: RE: [V1] app/testpmd: restore VXLAN-GPE support
Date: Tue, 23 Jul 2024 06:29:05 +0000	[thread overview]
Message-ID: <IA1PR12MB60198017ECF1CF2EF3867D17B3A92@IA1PR12MB6019.namprd12.prod.outlook.com> (raw)
In-Reply-To: <86e62944-35f3-475c-a035-e9ef1be00a7b@amd.com>

> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@amd.com>
> Sent: Monday, July 22, 2024 10:44 PM
> To: Minggang(Gavin) Li <gavinl@nvidia.com>; Matan Azrad <matan@nvidia.com>;
> Slava Ovsiienko <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>; NBU-
> Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>; Aman Singh
> <aman.deep.singh@intel.com>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>
> Subject: Re: [V1] app/testpmd: restore VXLAN-GPE support
> 
> On 7/17/2024 8:11 AM, Gavin Li wrote:
> > diff --git a/app/test-pmd/cmdline_flow.c b/app/test-pmd/cmdline_flow.c
> > index a76b44bf39..51a8d4993e 100644
> > --- a/app/test-pmd/cmdline_flow.c
> > +++ b/app/test-pmd/cmdline_flow.c
> > @@ -423,6 +423,12 @@ enum index {
> >  	ITEM_GENEVE_VNI,
> >  	ITEM_GENEVE_PROTO,
> >  	ITEM_GENEVE_OPTLEN,
> > +	ITEM_VXLAN_GPE,
> > +	ITEM_VXLAN_GPE_VNI,
> > +	ITEM_VXLAN_GPE_PROTOCOL,
> > +	ITEM_VXLAN_GPE_FLAGS,
> > +	ITEM_VXLAN_GPE_RSVD0,
> > +	ITEM_VXLAN_GPE_RSVD1,
> >
> 
> With this addition we have both of following enum items, right?
> 'ITEM_VXLAN_GPE_PROTOCOL'
> 'ITEM_VXLAN_GPE_PROTO'
> 
> 'ITEM_VXLAN_GPE_PROTOCOL' is for the old usage, which was previously
> 'ITEM_VXLAN_GPE_PROTO'.
> 
> And 'ITEM_VXLAN_GPE_PROTO' is now for the new usage.
> 
> This is confusing, and looks like it may live with us for a while if we remove them
> on v25.11.
> 
> 
> Does it make sense to keep 'ITEM_VXLAN_GPE_PROTO' as it is, add new one with
> a name that is more obvious that it is for new VXLAN struct, and some more
> comment to explain the reasoning of this redundant enum items?
> 
> As these are testpmd internal, when old VXLAN structs removed, I assume we can
> easily rename new enum item back to 'ITEM_VXLAN_GPE_PROTO'. What do you
> think?
Sounds good. ACK


  reply	other threads:[~2024-07-23  6:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-17  7:11 Gavin Li
2024-07-19 20:24 ` Ferruh Yigit
2024-07-22  7:10   ` Minggang(Gavin) Li
2024-07-22  9:36     ` Ferruh Yigit
2024-07-22 13:04       ` Thomas Monjalon
2024-07-22 13:41         ` Ferruh Yigit
2024-07-22 14:43 ` Ferruh Yigit
2024-07-23  6:29   ` Minggang(Gavin) Li [this message]
2024-07-23  7:37 ` [V2] " Gavin Li
2024-07-23  8:05   ` Ferruh Yigit
2024-07-23 14:09     ` Minggang(Gavin) Li
2024-07-23 14:26   ` [V3] " Gavin Li
2024-07-23 16:13     ` Ferruh Yigit
2024-07-23 16:48     ` 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=IA1PR12MB60198017ECF1CF2EF3867D17B3A92@IA1PR12MB6019.namprd12.prod.outlook.com \
    --to=gavinl@nvidia.com \
    --cc=aman.deep.singh@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@nvidia.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).