All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tal Shnaiderman <talshn@nvidia.com>
To: <dev@dpdk.org>
Cc: <thomas@monjalon.net>, <matan@nvidia.com>, <rasland@nvidia.com>,
	<asafp@nvidia.com>, <odia@nvidia.com>
Subject: [dpdk-dev] [PATCH] net/mlx5: add TCP and IPv6 to supported flow items list in Windows
Date: Tue, 1 Jun 2021 15:49:50 +0300	[thread overview]
Message-ID: <20210601124950.15908-1-talshn@nvidia.com> (raw)

WINOF2 2.70 Windows kernel driver allows DevX rule creation
of types TCP and IPv6.

Added the types to the supported items in mlx5_flow_os_item_supported
to allow them to be created in the PMD.

Signed-off-by: Tal Shnaiderman <talshn@nvidia.com>
---
 drivers/net/mlx5/windows/mlx5_flow_os.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/net/mlx5/windows/mlx5_flow_os.h b/drivers/net/mlx5/windows/mlx5_flow_os.h
index 26c3e59789..df92f25ce6 100644
--- a/drivers/net/mlx5/windows/mlx5_flow_os.h
+++ b/drivers/net/mlx5/windows/mlx5_flow_os.h
@@ -42,6 +42,8 @@ mlx5_flow_os_item_supported(int item)
 	case RTE_FLOW_ITEM_TYPE_ETH:
 	case RTE_FLOW_ITEM_TYPE_IPV4:
 	case RTE_FLOW_ITEM_TYPE_UDP:
+	case RTE_FLOW_ITEM_TYPE_TCP:
+	case RTE_FLOW_ITEM_TYPE_IPV6:
 		return true;
 	default:
 		return false;
-- 
2.16.1.windows.4


             reply	other threads:[~2021-06-01 12:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 12:49 Tal Shnaiderman [this message]
2021-06-17 16:07 ` [dpdk-dev] [PATCH v2 0/2] Add types to supported flow items in Windows Tal Shnaiderman
2021-06-17 16:07   ` [dpdk-dev] [PATCH v2 1/2] net/mlx5: add TCP and IPv6 to supported flow items list " Tal Shnaiderman
2021-06-22 15:34     ` [dpdk-dev] [PATCH v3] " Tal Shnaiderman
2021-06-23 11:56       ` Matan Azrad
2021-06-28  8:32       ` Raslan Darawsheh
2021-06-17 16:07   ` [dpdk-dev] [PATCH v2 2/2] doc: description of new steering rules support " Tal Shnaiderman

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=20210601124950.15908-1-talshn@nvidia.com \
    --to=talshn@nvidia.com \
    --cc=asafp@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=odia@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=thomas@monjalon.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.