From: Maayan Kashani <mkashani@nvidia.com>
To: <dev@dpdk.org>
Cc: <mkashani@nvidia.com>, <dsosnowski@nvidia.com>, <rasland@nvidia.com>
Subject: [PATCH 0/3] Non template to HWS fixes
Date: Tue, 28 Jan 2025 09:54:02 +0200 [thread overview]
Message-ID: <20250128075406.175330-1-mkashani@nvidia.com> (raw)
Few fixes for non template mode on top of HWS.
Maayan Kashani (3):
net/mlx5: fix limitation of actions per rule
net/mlx5: fix crash in non template metadata split
net/mlx5: fix flow flush for non-template flows
drivers/net/mlx5/mlx5_flow.c | 1 -
drivers/net/mlx5/mlx5_flow.h | 2 +-
drivers/net/mlx5/mlx5_flow_hw.c | 3 ---
drivers/net/mlx5/mlx5_nta_split.c | 28 +++++++++++++++-------------
4 files changed, 16 insertions(+), 18 deletions(-)
--
2.21.0
next reply other threads:[~2025-01-28 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 7:54 Maayan Kashani [this message]
2025-01-28 7:54 ` [PATCH 1/3] net/mlx5: fix limitation of actions per rule Maayan Kashani
2025-01-28 7:54 ` [PATCH 2/3] net/mlx5: fix crash in non template metadata split Maayan Kashani
2025-01-28 7:54 ` [PATCH 3/3] net/mlx5: fix flow flush for non-template flows Maayan Kashani
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=20250128075406.175330-1-mkashani@nvidia.com \
--to=mkashani@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=rasland@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).