From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Gavin Li <gavinl@nvidia.com>,
matan@nvidia.com, viacheslavo@nvidia.com, orika@nvidia.com,
thomas@monjalon.net
Cc: dev@dpdk.org, rasland@nvidia.com
Subject: Re: [V3 0/2] net: extend VXLAN header to support more extensions
Date: Tue, 11 Jun 2024 15:53:10 +0100 [thread overview]
Message-ID: <7530ad17-10c2-448e-89d1-cb521be34634@amd.com> (raw)
In-Reply-To: <20240605080953.534998-1-gavinl@nvidia.com>
On 6/5/2024 9:09 AM, Gavin Li wrote:
> In this patch series, all the VXLAN extension header will be merged with
> VXLAN as union if the overlapped field has different format among
> protocols. The existing VXLAN-GPE will be marked as deprecated and new
> extensions of VXLAN should be added to VXLAN instead of a new RTE item.
>
> RFC
> https://patches.dpdk.org/project/dpdk/patch/20240130112520.1971315-2-gavinl@nvidia.com/
>
> PMD changes
> https://patches.dpdk.org/project/dpdk/patch/20240514032131.153409-1-rongweil@nvidia.com/
>
> Gavin Li (2):
> net: extend VXLAN header to support more extensions
> ---
> changelog:
> v1->v2
> - removed deprecation (removal) note, it should be decided later
> - reworded deprecation comments to use @see for replacements
> - merged bits in a single place to avoid redefinitions
> - documented all bits
> - move big endian bit-fields first as it is the networking standard
> ---
> app/testpmd: support matching any VXLAN field
> ---
> changelog:
> v1->v2
> - add all supported bits in testpmd command line
> - documented all bits in testpmd doc
> v2->v3
> - add three bytes rsvd0 fields in testpmd command line
> - remove rsvd_gpe from testpmd command line
> - remove all existing "vxlan-gpe" in testpmd and doc
> - consistent naming of "VXLAN GPE" and "VXLAN GBP"
> - other minor naming issues
>
Series applied to dpdk-next-net/main, thanks.
Resolved conflict because of 'last_rsvd' modification in
'rte_vxlan_hdr', please double check the final code.
next prev parent reply other threads:[~2024-06-11 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 6:27 [V2 " Gavin Li
2024-06-04 6:27 ` [V2 1/2] " Gavin Li
2024-06-05 8:09 ` [V3 0/2] " Gavin Li
2024-06-05 8:09 ` [V3 1/2] " Gavin Li
2024-06-05 8:09 ` [V3 2/2] app/testpmd: support matching any VXLAN field Gavin Li
2024-06-11 14:53 ` Ferruh Yigit [this message]
2024-06-04 6:27 ` [V2 2/2] app/testpmd: introduce VXLAN-GBP and VXLAN-GPE fields Gavin Li
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=7530ad17-10c2-448e-89d1-cb521be34634@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=gavinl@nvidia.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).