From: Raslan Darawsheh <rasland@nvidia.com>
To: Gavin Li <gavinl@nvidia.com>,
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>,
Nelio Laranjeiro <nelio.laranjeiro@6wind.com>,
Yongseok Koh <yskoh@mellanox.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] net/mlx5: align PF and VF/SF MAC addresses handling
Date: Thu, 22 May 2025 11:44:24 +0300 [thread overview]
Message-ID: <3be89bb7-7ad5-4002-8dc9-b9067164d8da@nvidia.com> (raw)
In-Reply-To: <20250516071032.4357-1-gavinl@nvidia.com>
Hi,
On 16/05/2025 10:10 AM, Gavin Li wrote:
> In the mlx5_dev_spawn function, the Virtual Function (VF) synchronizes MAC
> addresses from the kernel using netlink. It queries the netdev-configured
> MACs and populates the list in the PMD device data, including multicast
> MAC addresses. These addresses are later used for control flow creation,
> allowing traffic for the listed MACs to be received. However, the Physical
> Function (PF) does not synchronize with the kernel and thus does not add
> any multicast MAC address rules when enabling traffic. This discrepancy
> causes the IFF_ALLMULTI ioctl code to malfunction, as it fails to disable
> all multicast traffic, leaving the VF still able to see it.
>
> To align PF and VF behavior, only unicast MAC address flows should be
> added.
>
> Fixes: 272733b5ebfd ("net/mlx5: use flow to enable unicast traffic")
> Cc: stable@dpdk.org
> Signed-off-by: Gavin Li <gavinl@nvidia.com>
> ---
Patch applied to next-net-mlx,
--
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2025-05-22 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 7:10 Gavin Li
2025-05-19 11:20 ` Slava Ovsiienko
2025-05-22 8:44 ` 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=3be89bb7-7ad5-4002-8dc9-b9067164d8da@nvidia.com \
--to=rasland@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=gavinl@nvidia.com \
--cc=matan@nvidia.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=orika@nvidia.com \
--cc=stable@dpdk.org \
--cc=suanmingm@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.com \
--cc=yskoh@mellanox.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).