From: Gavin Li <gavinl@nvidia.com>
To: <dev@dpdk.org>, <thomas@monjalon.net>, <orika@nvidia.com>,
<aman.deep.singh@intel.com>, <yuying.zhang@intel.com>,
<dsosnowski@nvidia.com>, <viacheslavo@nvidia.com>,
<suanmingm@nvidia.com>, <matan@nvidia.com>
Cc: <jiaweiw@nvidia.com>, <rasland@nvidia.com>
Subject: [V1 1/5] net/mlx5: support VXLAN-GPE flags matching
Date: Fri, 12 Jan 2024 10:02:06 +0200 [thread overview]
Message-ID: <20240112080210.1288356-2-gavinl@nvidia.com> (raw)
In-Reply-To: <20240112080210.1288356-1-gavinl@nvidia.com>
This commit adds support for matching on the flags field of VXLAN-GPE
header (the first 8-bits).
Signed-off-by: Gavin Li <gavinl@nvidia.com>
Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
---
drivers/net/mlx5/mlx5_flow.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/mlx5/mlx5_flow.c b/drivers/net/mlx5/mlx5_flow.c
index 85e8c77c81..ffa183dc1b 100644
--- a/drivers/net/mlx5/mlx5_flow.c
+++ b/drivers/net/mlx5/mlx5_flow.c
@@ -3292,6 +3292,7 @@ mlx5_flow_validate_item_vxlan_gpe(const struct rte_flow_item *item,
struct rte_flow_item_vxlan_gpe nic_mask = {
.vni = "\xff\xff\xff",
.protocol = 0xff,
+ .flags = 0xff,
};
if (!priv->sh->config.l3_vxlan_en)
--
2.39.1
next prev parent reply other threads:[~2024-01-12 8:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 8:02 [V1 0/5] support VXLAN-GPE header fields(flags, rsvd0 and rsvd1) matching Gavin Li
2024-01-12 8:02 ` Gavin Li [this message]
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
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=20240112080210.1288356-2-gavinl@nvidia.com \
--to=gavinl@nvidia.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=jiaweiw@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=suanmingm@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).