From: Eli Britstein <elibr@nvidia.com> To: <dev@dpdk.org> Cc: Ferruh Yigit <ferruh.yigit@intel.com>, <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>, <stable@dpdk.org> Subject: [dpdk-stable] [PATCH V2 2/2] net/mlx5: add support for more tunnel types Date: Thu, 23 Sep 2021 11:43:01 +0300 Message-ID: <20210923084301.5139-2-elibr@nvidia.com> (raw) In-Reply-To: <20210923084301.5139-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. Fixes: 4ec6360de37d ("net/mlx5: implement tunnel offload") Cc: stable@dpdk.org 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 c914a7120c..6a03fc52d7 100644 --- a/drivers/net/mlx5/mlx5_flow.c +++ b/drivers/net/mlx5/mlx5_flow.c @@ -9123,6 +9123,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-23 8:44 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <f07404a3-bd3a-aaad-3194-01159bb762a4@intel.com> 2021-09-23 8:43 ` [dpdk-stable] [PATCH V2 1/2] app/testpmd: add " Eli Britstein 2021-09-23 8:43 ` Eli Britstein [this message] 2021-10-19 21:52 ` [dpdk-stable] [dpdk-dev] [PATCH V2 2/2] net/mlx5: add support for more " Ferruh Yigit 2021-10-14 17:15 ` [dpdk-stable] [PATCH V2 1/2] app/testpmd: add " Ferruh Yigit 2021-10-14 18:29 ` Gregory Etelson 2021-10-19 21:52 ` [dpdk-stable] [dpdk-dev] " 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=20210923084301.5139-2-elibr@nvidia.com \ --to=elibr@nvidia.com \ --cc=dev@dpdk.org \ --cc=ferruh.yigit@intel.com \ --cc=getelson@nvidia.com \ --cc=matan@nvidia.com \ --cc=shahafs@nvidia.com \ --cc=stable@dpdk.org \ --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
patches for DPDK stable branches This inbox may be cloned and mirrored by anyone: git clone --mirror http://inbox.dpdk.org/stable/0 stable/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 stable stable/ http://inbox.dpdk.org/stable \ stable@dpdk.org public-inbox-index stable Example config snippet for mirrors. Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.stable AGPL code for this site: git clone https://public-inbox.org/public-inbox.git