From: Raslan Darawsheh <rasland@nvidia.com>
To: Ophir Munk <ophirmu@nvidia.com>,
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 V2 0/4] mlx5 unified fdb
Date: Wed, 26 Feb 2025 16:12:29 +0000 [thread overview]
Message-ID: <CH3PR12MB8460D282CC0E6F88B908AD85CFC22@CH3PR12MB8460.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20250226083846.4023622-1-ophirmu@nvidia.com>
Hi,
From: Ophir Munk <ophirmu@nvidia.com>
Sent: Wednesday, February 26, 2025 10:38 AM
To: Dariusz Sosnowski; Slava Ovsiienko; Bing Zhao; Ori Kam; Suanming Mou; Matan Azrad
Cc: dev@dpdk.org; Raslan Darawsheh
Subject: [PATCH V2 0/4] mlx5 unified fdb
V1: initial version
V2: rebase + determine unified fdb based on FW capability
Bing Zhao (1):
net/mlx5: remove unneeded FDB flag on representor action
Ophir Munk (3):
common/mlx5: support FDB unified capability query
net/mlx5: support FDB unified domain
net/mlx5/hws: allow different types in miss validation
drivers/common/mlx5/mlx5_devx_cmds.c | 3 +
drivers/common/mlx5/mlx5_devx_cmds.h | 1 +
drivers/net/mlx5/hws/mlx5dr_table.c | 18 +-
drivers/net/mlx5/linux/mlx5_os.c | 11 +
drivers/net/mlx5/mlx5.h | 8 +
drivers/net/mlx5/mlx5_flow_hw.c | 521 ++++++++++++++++++++++++-----------
drivers/net/mlx5/mlx5_flow_meter.c | 16 +-
drivers/net/mlx5/mlx5_flow_quota.c | 9 +-
drivers/net/mlx5/mlx5_hws_cnt.c | 9 +-
9 files changed, 429 insertions(+), 167 deletions(-)
--
2.8.4
rebased squashed second and third patch together,
series applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2025-02-26 16:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250225120213.2968616-0-ophirmu@nvidia.com>
2025-02-26 8:38 ` Ophir Munk
2025-02-26 8:38 ` [PATCH V2 1/4] common/mlx5: support FDB unified capability query Ophir Munk
2025-02-26 9:12 ` Dariusz Sosnowski
2025-02-26 8:38 ` [PATCH V2 2/4] net/mlx5: support FDB unified domain Ophir Munk
2025-02-26 9:13 ` Dariusz Sosnowski
2025-02-26 8:38 ` [PATCH V2 3/4] net/mlx5: remove unneeded FDB flag on representor action Ophir Munk
2025-02-26 9:13 ` Dariusz Sosnowski
2025-02-26 8:38 ` [PATCH V2 4/4] net/mlx5/hws: allow different types in miss validation Ophir Munk
2025-02-26 9:13 ` Dariusz Sosnowski
2025-02-26 16:12 ` 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=CH3PR12MB8460D282CC0E6F88B908AD85CFC22@CH3PR12MB8460.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=ophirmu@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).