From: Eli Britstein <elibr@nvidia.com>
To: <dev@dpdk.org>
Cc: <xiaoyun.li@intel.com>, Matan Azrad <matan@nvidia.com>,
Shahaf Shuler <shahafs@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
"Gregory Etelson" <getelson@nvidia.com>,
Eli Britstein <elibr@nvidia.com>
Subject: [dpdk-dev] [PATCH 2/2] net/mlx5: add support for more tunnel types
Date: Mon, 13 Sep 2021 17:25:35 +0300 [thread overview]
Message-ID: <20210913142535.9084-2-elibr@nvidia.com> (raw)
In-Reply-To: <20210913142535.9084-1-elibr@nvidia.com>
Accept RTE_FLOW_ITEM_TYPE_GRE, RTE_FLOW_ITEM_TYPE_NVGRE and
RTE_FLOW_ITEM_TYPE_GENEVE as valid tunnel types.
Signed-off-by: Eli Britstein <elibr@nvidia.com>
---
drivers/net/mlx5/mlx5_flow.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/net/mlx5/mlx5_flow.c b/drivers/net/mlx5/mlx5_flow.c
index 4762fa0f5f..a2810c4be3 100644
--- a/drivers/net/mlx5/mlx5_flow.c
+++ b/drivers/net/mlx5/mlx5_flow.c
@@ -9099,6 +9099,9 @@ mlx5_flow_tunnel_validate(struct rte_eth_dev *dev,
err_msg = "unsupported tunnel type";
goto out;
case RTE_FLOW_ITEM_TYPE_VXLAN:
+ case RTE_FLOW_ITEM_TYPE_GRE:
+ case RTE_FLOW_ITEM_TYPE_NVGRE:
+ case RTE_FLOW_ITEM_TYPE_GENEVE:
break;
}
--
2.28.0.2311.g225365fb51
next prev parent reply other threads:[~2021-09-13 14:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 14:25 [dpdk-dev] [PATCH 1/2] app/testpmd: add " Eli Britstein
2021-09-13 14:25 ` Eli Britstein [this message]
2021-10-18 8:48 ` [dpdk-dev] [PATCH 2/2] net/mlx5: add support for more " Slava Ovsiienko
2021-09-20 15:57 ` [dpdk-dev] [PATCH 1/2] app/testpmd: add " Ferruh Yigit
2021-09-23 8:43 ` [dpdk-dev] [PATCH V2 " Eli Britstein
2021-09-23 8:43 ` [dpdk-dev] [PATCH V2 2/2] net/mlx5: add support for more " Eli Britstein
2021-10-19 21:52 ` Ferruh Yigit
2021-10-14 17:15 ` [dpdk-dev] [PATCH V2 1/2] app/testpmd: add " Ferruh Yigit
2021-10-14 18:29 ` Gregory Etelson
2021-10-19 21:52 ` Ferruh Yigit
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=20210913142535.9084-2-elibr@nvidia.com \
--to=elibr@nvidia.com \
--cc=dev@dpdk.org \
--cc=getelson@nvidia.com \
--cc=matan@nvidia.com \
--cc=shahafs@nvidia.com \
--cc=viacheslavo@nvidia.com \
--cc=xiaoyun.li@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).