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 v2 2/2] doc: description of new steering rules support in Windows
Date: Thu, 17 Jun 2021 19:07:46 +0300 [thread overview]
Message-ID: <20210617160746.9228-3-talshn@nvidia.com> (raw)
In-Reply-To: <20210617160746.9228-1-talshn@nvidia.com>
Added description of new rules support in Windows
kernel driver WINOF2 2.70
Signed-off-by: Tal Shnaiderman <talshn@nvidia.com>
---
doc/guides/nics/mlx5.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 83299646dd..eb44a070b1 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -123,6 +123,9 @@ Limitations
- IPv4/UDP with CVLAN filtering
- Unicast MAC filtering
+ - Additional rules are supported from WinOF2 version 2.70:
+ - IPv4/TCP with CVLAN filtering
+ - L4 steering rules for port RSS of UDP, TCP and IP
- For secondary process:
--
2.16.1.windows.4
prev parent reply other threads:[~2021-06-17 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 12:49 [dpdk-dev] [PATCH] net/mlx5: add TCP and IPv6 to supported flow items list " Tal Shnaiderman
2021-06-17 16:07 ` [dpdk-dev] [PATCH v2 0/2] Add types to supported flow items " 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 ` Tal Shnaiderman [this message]
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=20210617160746.9228-3-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 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).