From: Matan Azrad <matan@nvidia.com>
To: Tal Shnaiderman <talshn@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
Raslan Darawsheh <rasland@nvidia.com>,
Asaf Penso <asafp@nvidia.com>, Odi Assli <odia@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH v3] net/mlx5: add TCP and IPv6 to supported flow items list in Windows
Date: Wed, 23 Jun 2021 11:56:10 +0000 [thread overview]
Message-ID: <DM4PR12MB538939A8BDF3FCA2696A970EDF089@DM4PR12MB5389.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210622153450.12324-1-talshn@nvidia.com>
From: Tal Shnaiderman
> 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.
>
> Added description of new rules support in Windows kernel driver WINOF2
> 2.70 to the mlx5 driver guide.
>
> Signed-off-by: Tal Shnaiderman <talshn@nvidia.com>
Acked-by: Matan Azrad <matan@nvidia.com>
next prev parent reply other threads:[~2021-06-23 11:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 12:49 [dpdk-dev] [PATCH] " 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 [this message]
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=DM4PR12MB538939A8BDF3FCA2696A970EDF089@DM4PR12MB5389.namprd12.prod.outlook.com \
--to=matan@nvidia.com \
--cc=asafp@nvidia.com \
--cc=dev@dpdk.org \
--cc=odia@nvidia.com \
--cc=rasland@nvidia.com \
--cc=talshn@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).