public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Maayan Kashani <mkashani@nvidia.com>, dev@dpdk.org
Subject: Re: [PATCH 0/4] net/mlx5: future HW devargs defaults and fixes
Date: Thu, 5 Feb 2026 18:06:21 +0200	[thread overview]
Message-ID: <32549b6d-89d0-4754-ab0e-8cb271afa676@nvidia.com> (raw)
In-Reply-To: <20260112092439.14843-1-mkashani@nvidia.com>

Hi,

On 12/01/2026 11:24 AM, Maayan Kashani wrote:
> This patch series contains bug fixes for the mlx5 PMD, primarily
> addressing issues with Hardware Steering (HWS) and flow devarg handling.
> 
> Summary of changes:
> 
> 1. drivers: fix flow devarg handling for future HW
>     Addresses SWS (Software Steering) deprecation on future hardware
>     generations (e.g., ConnectX-9). Updates default behavior for
>     dv_flow_en and allow_duplicate_pattern devargs based on device
>     capabilities, with proper error handling and user feedback.
> 
> 2. net/mlx5: fix default memzone requirements in HWS
>     Fixes memzone exhaustion when probing setups with ~1K SFs. The
>     default HWS sync flow API configuration was allocating unnecessary
>     rings (flow_transfer_pending/completed) that are only used with
>     async flow API. This patch removes the unnecessary allocations to
>     stay within memzone limits.
> 
> 3. net/mlx5: fix internal HWS pattern template creation
>     Improves PMD initialization time by separating pattern templates
>     into internal and external categories. Internal templates (created
>     by PMD) skip expensive validations, while application-provided
>     templates remain fully validated.
> 
> 4. net/mlx5: fix redundant control rules in promiscuous mode
>     Removes redundant DMAC and multicast/broadcast control flow rules
>     when promiscuous mode is enabled, as the device already receives
>     all traffic in this mode.
> 
> All patches are targeted for stable backport.
> 
> Dariusz Sosnowski (1):
>    net/mlx5: fix default memzone requirements in HWS
> 
> Maayan Kashani (3):
>    drivers: fix flow devarg handling for future HW
>    net/mlx5: fix internal HWS pattern template creation
>    net/mlx5: fix redundant control rules in promiscuous mode
> 
>   doc/guides/nics/mlx5.rst             |  11 ++-
>   drivers/common/mlx5/mlx5_devx_cmds.c |  18 ++++
>   drivers/common/mlx5/mlx5_devx_cmds.h |   6 ++
>   drivers/common/mlx5/mlx5_prm.h       |  14 +++-
>   drivers/net/mlx5/mlx5.c              |  71 +++++++++++++++-
>   drivers/net/mlx5/mlx5_flow_hw.c      | 121 ++++++++++++++++++++-------
>   drivers/net/mlx5/mlx5_trigger.c      |  16 ++--
>   7 files changed, 214 insertions(+), 43 deletions(-)
> 

Series applied to next-net-mlx,

Kindest regards
Raslan Darawsheh


      parent reply	other threads:[~2026-02-05 16:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12  9:24 [PATCH 0/4] net/mlx5: future HW devargs defaults and fixes Maayan Kashani
2026-01-12  9:24 ` [PATCH 1/4] drivers: fix flow devarg handling for future HW Maayan Kashani
2026-01-12 18:17   ` Dariusz Sosnowski
2026-01-13  1:20   ` Stephen Hemminger
2026-01-12  9:24 ` [PATCH 2/4] net/mlx5: fix default memzone requirements in HWS Maayan Kashani
2026-02-11 14:38   ` Bing Zhao
2026-02-12  9:02     ` Dariusz Sosnowski
2026-01-12  9:24 ` [PATCH 3/4] net/mlx5: fix internal HWS pattern template creation Maayan Kashani
2026-01-12 18:18   ` Dariusz Sosnowski
2026-01-12  9:24 ` [PATCH 4/4] net/mlx5: fix redundant control rules in promiscuous mode Maayan Kashani
2026-01-12 18:19   ` Dariusz Sosnowski
2026-01-18 11:40   ` Maayan Kashani
2026-01-14 17:31 ` [PATCH 0/4] net/mlx5: future HW devargs defaults and fixes Stephen Hemminger
2026-02-05 16:06 ` 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=32549b6d-89d0-4754-ab0e-8cb271afa676@nvidia.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=mkashani@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