From: Ido Schimmel <idosch@idosch.org>
To: Mrinmoy Ghosh <mrghosh@cisco.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org,
Mrinmoy Ghosh <mrinmoy_g@hotmail.com>,
Patrice Brissette <pbrisset@cisco.com>,
razor@blackwall.org
Subject: Re: [PATCH] net: bridge: vxlan: Protocol field in bridge fdb
Date: Wed, 20 Aug 2025 16:18:10 +0300 [thread overview]
Message-ID: <aKXLEiY8gd0sNGrW@shredder> (raw)
In-Reply-To: <20250818175258.275997-1-mrghosh@cisco.com>
+ Nik
Please use scripts/get_maintainer.pl when submitting a patch.
On Mon, Aug 18, 2025 at 05:52:58PM +0000, Mrinmoy Ghosh wrote:
> This is to add optional "protocol" field for bridge fdb entries.
> The introduction of the 'protocol' field in the bridge FDB for EVPN Multihome, addresses the need to distinguish between MAC addresses learned via the control plane and those learned via the data plane with data plane aging. Specifically:
> * A MAC address in an EVPN Multihome environment can be learned either through the control plane (static MAC) or the data plane (dynamic MAC with aging).
> * The 'protocol' field uses values such as 'HW' for data plane dynamic MACs and 'ZEBRA' for control plane static MACs.
> * This distinction allows the application to manage the MAC address state machine effectively during transitions, which can occur due to traffic hashing between EVPN Multihome peers or mobility of MAC addresses across EVPN peers.
> * By identifying the source of the MAC learning (control plane vs. data plane), the system can handle MAC aging and mobility more accurately, ensuring synchronization between control and data planes and improving stability and reliability in MAC route handling.
>
> This mechanism supports the complex state transitions and synchronization required in EVPN Multihome scenarios, where MAC addresses may move or be learned differently depending on network events and traffic patterns.
[...]
> Signed-off-by: Mrinmoy Ghosh <mrghosh@cisco.com>
> Co-authored-by: Mrinmoy Ghosh <mrinmoy_g@hotmail.com>
> Co-authored-by: Patrice Brissette <pbrisset@cisco.com>
> ---
> drivers/net/vxlan/vxlan_core.c | 132 ++++++++++++++--------------
> drivers/net/vxlan/vxlan_private.h | 21 +++--
> drivers/net/vxlan/vxlan_vnifilter.c | 11 +--
> net/bridge/br.c | 4 +-
> net/bridge/br_fdb.c | 52 ++++++++---
> net/bridge/br_private.h | 5 +-
> 6 files changed, 127 insertions(+), 98 deletions(-)
Please read these two documents and make changes accordingly before
submitting a new version:
https://docs.kernel.org/process/submitting-patches.html
https://docs.kernel.org/process/maintainer-netdev.html
At the very least the patch should be split to a bridge patch and a
VXLAN patch. I will provide more comments later this week.
Thanks
next prev parent reply other threads:[~2025-08-20 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 17:52 [PATCH] net: bridge: vxlan: Protocol field in bridge fdb Mrinmoy Ghosh
2025-08-20 13:18 ` Ido Schimmel [this message]
2025-08-21 11:03 ` Ido Schimmel
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=aKXLEiY8gd0sNGrW@shredder \
--to=idosch@idosch.org \
--cc=bridge@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrghosh@cisco.com \
--cc=mrinmoy_g@hotmail.com \
--cc=netdev@vger.kernel.org \
--cc=pbrisset@cisco.com \
--cc=razor@blackwall.org \
/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