All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Minggang Li (Gavin)" <gavinl@nvidia.com>, Gavin Li <gavinl@nvidia.com>
Cc: matan@nvidia.com, viacheslavo@nvidia.com, orika@nvidia.com,
	Dariusz Sosnowski <dsosnowski@nvidia.com>,
	Bing Zhao <bingz@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>,
	stable@dpdk.org, dev@dpdk.org, rasland@nvidia.com,
	stable@dpdk.org
Subject: Re: [PATCH V3 2/2] net/mlx5: add support for flows targeting multicast MAC addresses
Date: Mon, 25 Aug 2025 16:52:07 +0200	[thread overview]
Message-ID: <3029429.o0KrE1Onz3@thomas> (raw)
In-Reply-To: <20250825141322.974335-3-gavinl@nvidia.com>

25/08/2025 16:13, Gavin Li:
> Rules for multicast MAC addresses are intended to filter multicast traffic
> and are managed through multicast MAC add/remove APIs.

You should name the functions to be explicit.
Also it is not only managed via DPDK API,
as you say below we also retrieve kernel addresses.

> 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.
> 
> Previously, flows for multicast MAC addresses were incorrectly disabled,
> causing the multicast MAC add API to stop working.

To be clear, it was blocking addresses added in DPDK,
not ones created in kernel, right?

> As a result, multicast
> traffic directed to those multicast MAC addresses was not received.
> 
> To resolve this and update the multicast MAC address rules, create them
> within mlx5_traffic_enable.

Actually you allow default rules for multicast addresses to be created.

> -		if (!memcmp(mac, &cmp, sizeof(*mac)) || rte_is_multicast_ether_addr(mac))
> +		/* Add flows for unicast and multicast mac addresses added by API. */
> +		if (!memcmp(mac, &cmp, sizeof(*mac)) ||
> +		    !BITFIELD_ISSET(priv->mac_own, i) ||
> +		    (dev->data->all_multicast && rte_is_multicast_ether_addr(mac)))
>  			continue;

PS: you forgot to use --in-reply-to to keep all versions in the same mail thread.



  reply	other threads:[~2025-08-25 14:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 14:13 [PATCH V3 0/2] resolve flow creation issue for multicast MAC addresses 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 [this message]
2025-08-27 14:05     ` Minggang(Gavin) Li
2025-08-29  9:08   ` [PATCH V4 0/2] resolve flow creation issue for " Gavin Li
2025-08-29  9:08     ` [PATCH V4 1/2] net/mlx5: update how MAC address bit-fields are used Gavin Li
2025-09-08  6:36       ` Slava Ovsiienko
2025-08-29  9:08     ` [PATCH V4 2/2] net/mlx5: add support for flows targeting multicast MAC addresses Gavin Li
2025-09-08  6:35       ` Slava Ovsiienko
2025-09-15  6:37     ` [PATCH V4 0/2] resolve flow creation issue for " Raslan Darawsheh

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=3029429.o0KrE1Onz3@thomas \
    --to=thomas@monjalon.net \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.