DPDK patches and discussions
 help / color / mirror / Atom feed
From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: "Minggang(Gavin) Li" <gavinl@nvidia.com>,
	Matan Azrad <matan@nvidia.com>,  Ori Kam <orika@nvidia.com>,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
	Dariusz Sosnowski <dsosnowski@nvidia.com>,
	Bing Zhao <bingz@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Raslan Darawsheh <rasland@nvidia.com>
Subject: RE: [PATCH V4 1/2] net/mlx5: update how MAC address bit-fields are used
Date: Mon, 8 Sep 2025 06:36:51 +0000	[thread overview]
Message-ID: <DS0PR12MB85613A5B9168391873AD79BFDF0CA@DS0PR12MB8561.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20250829090830.1049176-2-gavinl@nvidia.com>

> -----Original Message-----
> From: Minggang(Gavin) Li <gavinl@nvidia.com>
> Sent: Friday, August 29, 2025 12:08 PM
> To: Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>; NBU-Contact-
> Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>; Dariusz Sosnowski
> <dsosnowski@nvidia.com>; Bing Zhao <bingz@nvidia.com>; Suanming Mou
> <suanmingm@nvidia.com>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>
> Subject: [PATCH V4 1/2] net/mlx5: update how MAC address bit-fields are
> used
> 
> Previously, mac_own was a bit-field indicating the MAC addresses owned by
> the PMD, specifically marking those added to VFs by the PMD and allowing
> them to be flushed during exit.
> 
> With this commit, the bit-field now applies to all MAC addresses added by the
> PMD, including those for PF, VF, and SFs.
> 
> This patch does not introduce any changes in behavior; it continues to flush
> only the MAC added for VF, just as before. It serves as preparation for
> addressing the multicast MAC address issue.
> 
> Signed-off-by: Gavin Li <gavinl@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>

  reply	other threads:[~2025-09-08  6:36 UTC|newest]

Thread overview: 12+ 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
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 [this message]
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

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=DS0PR12MB85613A5B9168391873AD79BFDF0CA@DS0PR12MB8561.namprd12.prod.outlook.com \
    --to=viacheslavo@nvidia.com \
    --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=suanmingm@nvidia.com \
    --cc=thomas@monjalon.net \
    /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).