From: Raslan Darawsheh <rasland@nvidia.com>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH 0/3] net/mlx5: E-Switch and validation fixes
Date: Sun, 21 Jul 2024 13:58:05 +0000 [thread overview]
Message-ID: <MN0PR12MB605672CF01E113490D01E059CFAF2@MN0PR12MB6056.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240718095717.290960-1-dsosnowski@nvidia.com>
Hi,
From: Dariusz Sosnowski <dsosnowski@nvidia.com>
Sent: Thursday, July 18, 2024 12:57 PM
To: Slava Ovsiienko; Bing Zhao; Ori Kam; Suanming Mou; Matan Azrad
Cc: dev@dpdk.org; Raslan Darawsheh
Subject: [PATCH 0/3] net/mlx5: E-Switch and validation fixes
Patch 1 - Fixes a bug with fdb_def_rule_en device argument,
used to control default E-Switch flow rules created by mlx5 PMD.
Patches 2-3 - Fixes for flow rule validation in async flow API,
which were found during testing.
Dariusz Sosnowski (3):
net/mlx5: fix disabling E-Switch default flow rules
net/mlx5: fix action configuration validation
net/mlx5: fix RSS and queue action validation
drivers/net/mlx5/mlx5_flow_hw.c | 182 +++++++++++++++++---------------
drivers/net/mlx5/mlx5_trigger.c | 4 +-
drivers/net/mlx5/mlx5_txq.c | 13 ++-
3 files changed, 107 insertions(+), 92 deletions(-)
series applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2024-07-21 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 9:57 Dariusz Sosnowski
2024-07-18 9:57 ` [PATCH 1/3] net/mlx5: fix disabling E-Switch default flow rules Dariusz Sosnowski
2024-07-18 9:57 ` [PATCH 2/3] net/mlx5: fix action configuration validation Dariusz Sosnowski
2024-07-18 9:57 ` [PATCH 3/3] net/mlx5: fix RSS and queue action validation Dariusz Sosnowski
2024-07-21 13:58 ` 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=MN0PR12MB605672CF01E113490D01E059CFAF2@MN0PR12MB6056.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@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).