From: "Minggang Li(Gavin)" <gavinl@nvidia.com>
To: <matan@nvidia.com>, <viacheslavo@nvidia.com>, <orika@nvidia.com>,
<thomas@monjalon.net>, Dariusz Sosnowski <dsosnowski@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>,
Alex Vesker <valex@nvidia.com>, Rongwei Liu <rongweil@nvidia.com>
Cc: <dev@dpdk.org>, <rasland@nvidia.com>
Subject: [PATCH 1/2] doc: fix mlx5 VXLAN matching limitations
Date: Tue, 18 Feb 2025 12:33:21 +0200 [thread overview]
Message-ID: <20250218103322.166461-2-gavinl@nvidia.com> (raw)
In-Reply-To: <20250218103322.166461-1-gavinl@nvidia.com>
P bit of VXLAN-GPE and G bit of VXLAN-GBP should be set when matching the
protocols.
Fixes: 49765b78c81b ("net/mlx5/hws: match all VXLAN fields")
Signed-off-by: Minggang Li(Gavin) <gavinl@nvidia.com>
---
doc/guides/nics/mlx5.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 690b46a974..caf711ce67 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -339,6 +339,10 @@ Limitations
- For ConnectX-5, the UDP destination port must be the standard one (4789).
- Default UDP destination is 4789 if not explicitly specified.
- Group zero's behavior may differ which depends on FW.
+ - User should set different flags when matching on VXLAN-GPE/GBP:
+
+ - for VXLAN-GPE - P flag
+ - for VXLAN-GBP - G flag
- Matching on VXLAN-GPE header fields:
--
2.34.1
next prev parent reply other threads:[~2025-02-18 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 10:33 [PATCH 0/2] use flags from user if it is set Minggang Li(Gavin)
2025-02-18 10:33 ` Minggang Li(Gavin) [this message]
2025-02-18 10:56 ` [PATCH 1/2] doc: fix mlx5 VXLAN matching limitations Dariusz Sosnowski
2025-02-18 10:33 ` [PATCH 2/2] app/testpmd: use flags from user if it is set Minggang Li(Gavin)
2025-02-18 10:56 ` Dariusz Sosnowski
2025-02-20 20:58 ` [PATCH 0/2] " 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=20250218103322.166461-2-gavinl@nvidia.com \
--to=gavinl@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=rongweil@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=thomas@monjalon.net \
--cc=valex@nvidia.com \
--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).