From: Patrick Robb <probb@iol.unh.edu>
To: Gavin Li <gavinl@nvidia.com>
Cc: matan@nvidia.com, viacheslavo@nvidia.com, orika@nvidia.com,
thomas@monjalon.net, Dariusz Sosnowski <dsosnowski@nvidia.com>,
Bing Zhao <bingz@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
dev@dpdk.org, rasland@nvidia.com, stable@dpdk.org,
Dean Marx <dmarx@iol.unh.edu>,
Andrew Bailey <abailey@iol.unh.edu>
Subject: Re: [PATCH] net/mlx5: add support for flows targeting multicast MAC addresses
Date: Thu, 7 Aug 2025 13:40:49 -0400 [thread overview]
Message-ID: <CAJvnSUDkYY7-OJjVo2vgX1VEfXCF+xFSvZKBkU+8NDfEu+=KGA@mail.gmail.com> (raw)
In-Reply-To: <20250807115943.690540-1-gavinl@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 2873 bytes --]
Hi Gavin, I'm just flagging that this patch has a failure for the
dynamic_config testsuite's test_disable_promisc_multicast testcase.
It's a testpmd testcase which disables allmulticast on the port and then
verifies that a multicast packet sent to the DUT is dropped, then enables
allmulticast and verifies that a multicast packet is received. It looks
like your series is failing for the initial check (that the packet is
dropped when allmulticast is disabled).
I'm not sure why your series is failing if it is just allowing multicast
addrs to be stored in PMD device data. Maybe it is the case that your
series is allowing the multicast address to be added (correctly), and then
that is exposing an existing issue with disabling allmulticast on a port
with the PMD? Otherwise, I'm not sure.
https://doc.dpdk.org/api/rte__ethdev_8h.html#a2fe97cde3f374385ef0b12f61e7c30da
https://doc.dpdk.org/guides/testpmd_app_ug/testpmd_funcs.html#set-allmulti
If you want to verify that allmulticast disable is working properly for a
future version of your patch you can validate it with testpmd, or even
better just run the DTS testsuite. If you need any help setting up DTS the
students at UNH are available to help with that and I added them to the CC
list.
Thanks.
On Thu, Aug 7, 2025 at 8:06 AM Gavin Li <gavinl@nvidia.com> wrote:
> Rules for multicast MAC addresses are intended to filter multicast traffic
> and are managed through multicast MAC add/remove APIs. In mlx5_dev_spawn
> function, devices (PF, VFs, and SFs) retrieve the netdev-configured MAC
> addresses via netlink and store them in the PMD device data, which
> includes multicast MAC addresses.
>
> To update multicast MAC address rules, create them within
> mlx5_traffic_enable.
>
> Fixes: 2d0665a7f771 ("net/mlx5: align PF and VF/SF MAC address handling")
> Cc: stable@dpdk.org
>
> Signed-off-by: Gavin Li <gavinl@nvidia.com>
> ---
> drivers/net/mlx5/mlx5_trigger.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/mlx5/mlx5_trigger.c
> b/drivers/net/mlx5/mlx5_trigger.c
> index 6c6f228afd..6e82a8b021 100644
> --- a/drivers/net/mlx5/mlx5_trigger.c
> +++ b/drivers/net/mlx5/mlx5_trigger.c
> @@ -1813,7 +1813,8 @@ mlx5_traffic_enable(struct rte_eth_dev *dev)
> for (i = 0; i != MLX5_MAX_MAC_ADDRESSES; ++i) {
> struct rte_ether_addr *mac = &dev->data->mac_addrs[i];
>
> - if (!memcmp(mac, &cmp, sizeof(*mac)) ||
> rte_is_multicast_ether_addr(mac))
> + /* Add rules for unicast and multicast mac addresses
> synchronized from kernel. */
> + if (!memcmp(mac, &cmp, sizeof(*mac)))
> continue;
> memcpy(&unicast.hdr.dst_addr.addr_bytes,
> mac->addr_bytes,
> --
> 2.34.1
>
>
[-- Attachment #2: Type: text/html, Size: 3775 bytes --]
prev parent reply other threads:[~2025-08-07 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 11:59 Gavin Li
2025-08-07 17:40 ` Patrick Robb [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='CAJvnSUDkYY7-OJjVo2vgX1VEfXCF+xFSvZKBkU+8NDfEu+=KGA@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=abailey@iol.unh.edu \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=dsosnowski@nvidia.com \
--cc=gavinl@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=suanmingm@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).