From: Gavin Li <gavinl@nvidia.com>
To: <matan@nvidia.com>, <viacheslavo@nvidia.com>, <orika@nvidia.com>,
<thomas@monjalon.net>
Cc: <dev@dpdk.org>, <rasland@nvidia.com>
Subject: [PATCH V4 0/2] resolve flow creation issue for multicast MAC addresses
Date: Fri, 29 Aug 2025 12:08:28 +0300 [thread overview]
Message-ID: <20250829090830.1049176-1-gavinl@nvidia.com> (raw)
In-Reply-To: <20250825141322.974335-3-gavinl@nvidia.com>
A bug was introduced by commit 2d0665a7f771 ("net/mlx5: align PF and
VF/SF MAC address handling"). Flows for multicast MAC addresses would
not be created anymore.
This patch series are to fix the issue.
Minggang Li (Gavin) (2):
net/mlx5: update how MAC address bit-fields are used
net/mlx5: add support for flows targeting multicast MAC addresses
drivers/common/mlx5/linux/mlx5_nl.c | 26 ++++++++++++--------------
drivers/common/mlx5/linux/mlx5_nl.h | 8 ++++----
drivers/net/mlx5/linux/mlx5_os.c | 12 +++++++++---
drivers/net/mlx5/mlx5_trigger.c | 5 ++++-
4 files changed, 29 insertions(+), 22 deletions(-)
--
2.34.1
next prev parent reply other threads:[~2025-08-29 9:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 14:13 [PATCH V3 " Gavin Li
2025-08-25 14:13 ` [PATCH V3 1/2] net/mlx5: update how MAC address bit-fields are used Gavin Li
2025-08-25 14:54 ` Thomas Monjalon
2025-08-27 14:02 ` Minggang(Gavin) Li
2025-08-25 14:13 ` [PATCH V3 2/2] net/mlx5: add support for flows targeting multicast MAC addresses Gavin Li
2025-08-25 14:52 ` Thomas Monjalon
2025-08-27 14:05 ` Minggang(Gavin) Li
2025-08-29 9:08 ` Gavin Li [this message]
2025-08-29 9:08 ` [PATCH V4 1/2] net/mlx5: update how MAC address bit-fields are used Gavin Li
2025-08-29 9:08 ` [PATCH V4 2/2] net/mlx5: add support for flows targeting multicast MAC addresses Gavin Li
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=20250829090830.1049176-1-gavinl@nvidia.com \
--to=gavinl@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
--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).