From: Thomas Monjalon <thomas@monjalon.net>
To: 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>,
dev@dpdk.org, rasland@nvidia.com
Subject: Re: [PATCH V3 1/2] net/mlx5: update how MAC address bit-fields are used
Date: Mon, 25 Aug 2025 16:54:25 +0200 [thread overview]
Message-ID: <2010919.fIoEIV5pvu@thomas> (raw)
In-Reply-To: <20250825141322.974335-2-gavinl@nvidia.com>
25/08/2025 16:13, Gavin Li:
> 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. The process for flushing MAC
> addresses added to VFs by the PMD remains unchanged.
To be clear, there is no behaviour change in this patch?
You should mention the goal of this patch (preparation of a fix for multicast).
next prev parent reply other threads:[~2025-08-25 14:54 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 [this message]
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
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=2010919.fIoEIV5pvu@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=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.