From: Raslan Darawsheh <rasland@nvidia.com>
To: "Xueming(Steven) Li" <xuemingl@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Ori Kam <orika@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>
Cc: "Xueming(Steven) Li" <xuemingl@nvidia.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v2] net/mlx5: support symmetric RSS hash function
Date: Thu, 6 Jul 2023 15:17:13 +0000 [thread overview]
Message-ID: <BYAPR12MB30780041D987925CE5B663BFCF2CA@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230706115557.8114-1-xuemingl@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 2172 bytes --]
Hi,
> -----Original Message-----
> From: Xueming Li <xuemingl@nvidia.com>
> Sent: Thursday, July 6, 2023 2:56 PM
> To: Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>; Suanming Mou
> <suanmingm@nvidia.com>
> Cc: Xueming(Steven) Li <xuemingl@nvidia.com>; dev@dpdk.org
> Subject: [PATCH v2] net/mlx5: support symmetric RSS hash function
>
> This patch supports symmetric hash function that creating same
> hash result for bi-direction traffic which having reverse
> source and destination IP and L4 port.
>
> Since the hash algorithom is different than spec(XOR), leave a
fixed a typo algorithom -> algorithm
> warning in validation.
>
> Signed-off-by: Xueming Li <xuemingl@nvidia.com>
> ---
> doc/guides/nics/mlx5.rst | 4 ++++
> drivers/net/mlx5/mlx5.h | 3 +++
> drivers/net/mlx5/mlx5_devx.c | 11 ++++++++---
> drivers/net/mlx5/mlx5_flow.c | 10 ++++++++--
> drivers/net/mlx5/mlx5_flow.h | 5 +++++
> drivers/net/mlx5/mlx5_flow_dv.c | 13 ++++++++++++-
> drivers/net/mlx5/mlx5_flow_hw.c | 7 +++++++
> drivers/net/mlx5/mlx5_rx.h | 2 +-
> drivers/net/mlx5/mlx5_rxq.c | 8 +++++---
> 9 files changed, 53 insertions(+), 10 deletions(-)
>
> diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
> index b9843edbd9..20420c7feb 100644
> --- a/doc/guides/nics/mlx5.rst
> +++ b/doc/guides/nics/mlx5.rst
> @@ -110,6 +110,7 @@ Features
> and source only, destination only or both.
> - Several RSS hash keys, one for each flow type.
> - Default RSS operation with no hash key specification.
> +- Symmetric RSS function.
> - Configurable RETA table.
> - Link flow control (pause frame).
> - Support for multiple MAC addresses.
> @@ -708,6 +709,9 @@ Limitations
> The flow engine of a process cannot move from active to standby mode
> if preceding active application rules are still present and vice versa.
>
> +- The symmetric RSS function is supported by swapping source and
> desitination
Fixed typo desitination -> destination
Patch applied to next -net-mlx,
Kindest regards
Raslan Darawsheh
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 14545 bytes --]
prev parent reply other threads:[~2023-07-06 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 7:37 [PATCH] " Xueming Li
2023-06-30 7:54 ` [PATCH v1] " Xueming Li
2023-07-04 8:27 ` Ori Kam
2023-07-06 11:55 ` [PATCH v2] " Xueming Li
2023-07-06 15:07 ` Matan Azrad
2023-07-06 15:17 ` Raslan Darawsheh [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=BYAPR12MB30780041D987925CE5B663BFCF2CA@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@nvidia.com \
--cc=xuemingl@nvidia.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).