From: Thomas Monjalon <thomas@monjalon.net>
To: Gavin Li <gavinl@nvidia.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, orika@nvidia.com, aman.deep.singh@intel.com,
yuying.zhang@intel.com, dsosnowski@nvidia.com,
viacheslavo@nvidia.com, suanmingm@nvidia.com, matan@nvidia.com,
jiaweiw@nvidia.com, rasland@nvidia.com
Subject: Re: [V1 0/5] support VXLAN-GPE header fields(flags, rsvd0 and rsvd1) matching
Date: Mon, 19 Feb 2024 23:48:31 +0100 [thread overview]
Message-ID: <4674219.U3zVgo479M@thomas> (raw)
In-Reply-To: <20240219115017.02497c80@hermes.local>
19/02/2024 20:50, Stephen Hemminger:
> On Fri, 12 Jan 2024 10:02:05 +0200
> Gavin Li <gavinl@nvidia.com> wrote:
>
> > Previously, VXLAN-GPE in DPDK only supports VNI and next protocol header
> > fields. This patch series add support for flags and reserved field 0 and
> > 1.
> >
> > Below is the VXLAN-GPE header defined in the lasted draft.
> > 0 1 2 3
> > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > |R|R|Ver|I|P|B|O| Reserved |Next Protocol |
> > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > | VXLAN Network Identifier (VNI) | Reserved |
> > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> Would recommend against implementing anything in a draft RFC.
> Things can change. Learned the hard way when doing VXLAN driver for Linux.
> The hardcoded port value in the Linux VXLAN driver is wrong because it matched
> the draft RFC (got changed in final version). Because of strict compatibility
> requirements the Linux driver could not be changed to the correct value.
The problem is that standardization may be slow.
Would it be acceptable without any compatibility guarantee?
next prev parent reply other threads:[~2024-02-19 22:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 8:02 Gavin Li
2024-01-12 8:02 ` [V1 1/5] net/mlx5: support VXLAN-GPE flags matching Gavin Li
2024-01-12 8:02 ` [V1 2/5] app/testpmd: support VXLAN-GPE flags Gavin Li
2024-01-25 6:19 ` Singh, Aman Deep
2024-01-12 8:02 ` [V1 3/5] net/mlx5: support VXLAN-GPE reserved fields matching Gavin Li
2024-01-12 8:02 ` [V1 4/5] app/testpmd: support VXLAN-GPE reserved fields Gavin Li
2024-01-25 6:17 ` Singh, Aman Deep
2024-01-12 8:02 ` [V1 5/5] net/mlx5/hws: support VXLAN-GPE matching Gavin Li
2024-01-24 9:46 ` [V1 0/5] support VXLAN-GPE header fields(flags, rsvd0 and rsvd1) matching Raslan Darawsheh
2024-02-19 19:50 ` Stephen Hemminger
2024-02-19 22:48 ` Thomas Monjalon [this message]
2024-02-19 23:44 ` Stephen Hemminger
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=4674219.U3zVgo479M@thomas \
--to=thomas@monjalon.net \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=gavinl@nvidia.com \
--cc=jiaweiw@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stephen@networkplumber.org \
--cc=suanmingm@nvidia.com \
--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).