DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gavin Li <gavinl@nvidia.com>
To: <matan@nvidia.com>, <viacheslavo@nvidia.com>, <orika@nvidia.com>,
	<thomas@monjalon.net>
Cc: <dev@dpdk.org>, <rasland@nvidia.com>
Subject: [v1 0/2] extend VXLAN header to support more extensions
Date: Fri, 17 May 2024 11:07:33 +0300	[thread overview]
Message-ID: <20240517080735.1787616-1-gavinl@nvidia.com> (raw)

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
  app/testpmd: introduce VXLAN-GBP and VXLAN-GPE fields

 app/test-pmd/cmdline_flow.c                 | 40 ++++++++++++
 doc/guides/rel_notes/deprecation.rst        |  5 ++
 doc/guides/testpmd_app_ug/testpmd_funcs.rst |  4 ++
 lib/ethdev/rte_flow.h                       | 13 +++-
 lib/net/rte_vxlan.h                         | 69 +++++++++++++++++++--
 5 files changed, 125 insertions(+), 6 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-05-17  8:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17  8:07 Gavin Li [this message]
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

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=20240517080735.1787616-1-gavinl@nvidia.com \
    --to=gavinl@nvidia.com \
    --cc=dev@dpdk.org \
    --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).