From: Ori Kam <orika@nvidia.com>
To: "Minggang(Gavin) Li" <gavinl@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
Aman Singh <aman.deep.singh@intel.com>,
Yuying Zhang <yuying.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Raslan Darawsheh <rasland@nvidia.com>
Subject: RE: [v1 2/2] app/testpmd: introduce VXLAN-GBP and VXLAN-GPE fields
Date: Thu, 23 May 2024 08:20:16 +0000 [thread overview]
Message-ID: <DM5PR12MB466446D579DAE248F0CFE233D6F42@DM5PR12MB4664.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240517080735.1787616-3-gavinl@nvidia.com>
> -----Original Message-----
> From: Minggang(Gavin) Li <gavinl@nvidia.com>
> Sent: Friday, May 17, 2024 11:08 AM
> Subject: [v1 2/2] app/testpmd: introduce VXLAN-GBP and VXLAN-GPE fields
>
> After unification of VXLAN and all its extension protocols(VXLAN-GPE and
> VXLAN-GBP currently), all related RTE items should be spicified after
> 'vxlan'. And it's user's responsibility to specify correct UDP port for
> the protocol to be matched.
>
> Below are the examples to match standard VXLAN, VXLAN-GPE and VXLAN-
> GBP.
> To match standard vxlan,
> ... / udp dst is 4789 / vxlan ... / ...
> To match VXLAN-GBP group policy ID 4321,
> ... / udp dst is 4789 / vxlan group_policy_id is 4321 ... / ...
> To match VXLAN-GPE,
> ... / udp dst is 4790 / vxlan protocol is 2 ... / ...
>
> Signed-off-by: Gavin Li <gavinl@nvidia.com>
> Acked-by: Thomas Monjalon <thomas@monjalon.net>
> ---
Acked-by: Ori Kam <orika@nvidia.com>
Best,
Ori
prev parent reply other threads:[~2024-05-23 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 8:07 [v1 0/2] extend VXLAN header to support more extensions Gavin Li
2024-05-17 8:07 ` [v1 1/2] net: " Gavin Li
2024-05-17 8:07 ` [v1 2/2] app/testpmd: introduce VXLAN-GBP and VXLAN-GPE fields Gavin Li
2024-05-23 8:20 ` Ori Kam [this message]
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=DM5PR12MB466446D579DAE248F0CFE233D6F42@DM5PR12MB4664.namprd12.prod.outlook.com \
--to=orika@nvidia.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=gavinl@nvidia.com \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.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).