DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Raja Zidane <rzidane@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>
Subject: RE: [PATCH V5] net/mlx5: support ESP SPI match and RSS hash
Date: Sun, 15 May 2022 07:40:18 +0000	[thread overview]
Message-ID: <BYAPR12MB30781B3A7CCB2011BEE058F3CFCC9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220512091711.16894-1-rzidane@nvidia.com>

Hi,
> -----Original Message-----
> From: Raja Zidane <rzidane@nvidia.com>
> Sent: Thursday, May 12, 2022 12:17 PM
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>
> Subject: [PATCH V5] net/mlx5: support ESP SPI match and RSS hash
> 
> In packets with ESP header, The Inner IP will be encrypted, and its fields
> cannot be used for RSS hashing. So, ESP packets can be hashed only by the
> outer IP layer.
> So, when using RSS on ESP packets, hashing may not be efficient, because
> the fields used by the hash functions are only the Outer IPs, causing all traffic
> belonging to all tunnels between a given pair of GWs to land on one core.
> Adding the SPI hash field can extend the spreading of IPSec packets.
> 
> support matching on ESP SPI.
> Support RSS on ESP header by hashing SPI field.
> 
> Signed-off-by: Raja Zidane <rzidane@nvidia.com>
> ---
> V2: added doc.
> V3: fixed checkpatch.
> V4: rebase
> V5: rebase and doc.
>  doc/guides/nics/features/mlx5.ini      |  1 +
>  doc/guides/nics/mlx5.rst               |  1 +
>  doc/guides/rel_notes/release_22_07.rst |  2 +
> drivers/common/mlx5/linux/meson.build  |  2 +
>  drivers/common/mlx5/mlx5_prm.h         |  5 +-
>  drivers/net/mlx5/mlx5_defs.h           |  2 +-
>  drivers/net/mlx5/mlx5_devx.c           |  4 +-
>  drivers/net/mlx5/mlx5_flow.c           | 84 +++++++++++++++++++++++-
>  drivers/net/mlx5/mlx5_flow.h           | 20 ++++++
>  drivers/net/mlx5/mlx5_flow_dv.c        | 88 +++++++++++++++++++++++++-
>  10 files changed, 204 insertions(+), 5 deletions(-)
> 

Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh


      parent reply	other threads:[~2022-05-15  7:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 13:04 [PATCH] " Raja Zidane
2022-04-17  7:12 ` Raslan Darawsheh
2022-04-18 10:57 ` [PATCH V2] " Raja Zidane
2022-04-18 11:01   ` [PATCH V3] " Raja Zidane
2022-04-28 15:43     ` [PATCH V4] " Raja Zidane
2022-05-11  8:07       ` Matan Azrad
2022-05-12  9:17       ` [PATCH V5] " Raja Zidane
2022-05-12 15:05         ` Matan Azrad
2022-05-15  7:40         ` 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=BYAPR12MB30781B3A7CCB2011BEE058F3CFCC9@BYAPR12MB3078.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=rzidane@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).