public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Wei Fang <wei.fang@nxp•com>
To: "Wei Fang (OSS)" <wei.fang@oss•nxp.com>,
	Claudiu Manoil <claudiu.manoil@nxp•com>,
	Vladimir Oltean <vladimir.oltean@nxp•com>,
	Clark Wang <xiaoning.wang@nxp•com>,
	"andrew+netdev@lunn•ch" <andrew+netdev@lunn•ch>,
	"davem@davemloft•net" <davem@davemloft•net>,
	"edumazet@google•com" <edumazet@google•com>,
	"kuba@kernel•org" <kuba@kernel•org>,
	"pabeni@redhat•com" <pabeni@redhat•com>,
	"chleroy@kernel•org" <chleroy@kernel•org>,
	"andrew@lunn•ch" <andrew@lunn•ch>,
	"olteanv@gmail•com" <olteanv@gmail•com>
Cc: "imx@lists•linux.dev" <imx@lists•linux.dev>,
	"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
	"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
	"linuxppc-dev@lists•ozlabs.org" <linuxppc-dev@lists•ozlabs.org>,
	"linux-arm-kernel@lists•infradead.org"
	<linux-arm-kernel@lists•infradead.org>
Subject: RE: [PATCH net-next 0/9] net: dsa: netc: add bridge mode support
Date: Fri, 29 May 2026 01:53:04 +0000	[thread overview]
Message-ID: <DBBPR04MB7500385FABFC6DB0DF9792DF88162@DBBPR04MB7500.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20260527100217.794987-1-wei.fang@oss.nxp.com>

> This series adds bridge mode support to the NETC DSA switch driver,
> covering both VLAN-aware and VLAN-unaware operation.
> 
> The NETC switch manages forwarding through a set of hardware tables
> accessed via NTMP: the FDB table (FDBT), VLAN filter table (VFT), egress
> treatment table (ETT), and egress count table (ECT).  The series extends
> the NTMP layer with the operations required for bridging, then builds the
> DSA bridge callbacks on top.
> 
> Since all switch ports share the VFT, so only one VLAN-aware bridge is
> supported.
> 
> FDB aging is managed in software.  A periodic delayed work sweeps the
> table using the hardware activity element mechanism, with a default aging
> time of 300 seconds matching the IEEE 802.1Q standard.  Per-port entries
> are also flushed immediately on bridge leave and link-down events.
> 
> Wei Fang (9):
>   net: enetc: add interfaces to manage FDB entries
>   net: enetc: add "Update" and "Delete" operations to VLAN filter table
>   net: enetc: add interfaces to manage egress treatment table
>   net: enetc: add "Update" operation to the egress count table
>   net: dsa: netc: initialize the group bitmap of ETT and ECT
>   net: enetc: add helpers to set/clear table bitmap
>   net: dsa: netc: add VLAN filter table and egress treatment management
>   net: dsa: netc: add bridge mode support
>   net: dsa: netc: implement dynamic FDB entry aging
> 
>  drivers/net/dsa/netc/netc_main.c              | 882
> +++++++++++++++++-
>  drivers/net/dsa/netc/netc_switch.h            |  34 +
>  drivers/net/dsa/netc/netc_switch_hw.h         |   6 +
>  drivers/net/ethernet/freescale/enetc/ntmp.c   | 431 +++++++++
>  .../ethernet/freescale/enetc/ntmp_private.h   |  14 +
>  include/linux/fsl/ntmp.h                      |  60 ++
>  6 files changed, 1413 insertions(+), 14 deletions(-)
> 
> --
> 2.34.1

Sashi reported some issues for this series:
[1] https://sashiko.dev/#/patchset/20260527100217.794987-1-wei.fang%40oss.nxp.com
[2] https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260527100217.794987-1-wei.fang%40oss.nxp.com

Some of them are indeed potential issues, I will fix them in next version.
Any other comments are welcome, thanks.

--
pw-bot: cr



      parent reply	other threads:[~2026-05-29  1:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-27 10:02 [PATCH net-next 0/9] net: dsa: netc: add bridge mode support wei.fang
2026-05-27 10:02 ` [PATCH net-next 1/9] net: enetc: add interfaces to manage FDB entries wei.fang
2026-05-27 10:02 ` [PATCH net-next 2/9] net: enetc: add "Update" and "Delete" operations to VLAN filter table wei.fang
2026-05-27 10:02 ` [PATCH net-next 3/9] net: enetc: add interfaces to manage egress treatment table wei.fang
2026-05-27 10:02 ` [PATCH net-next 4/9] net: enetc: add "Update" operation to the egress count table wei.fang
2026-05-27 10:02 ` [PATCH net-next 5/9] net: dsa: netc: initialize the group bitmap of ETT and ECT wei.fang
2026-05-27 10:02 ` [PATCH net-next 6/9] net: enetc: add helpers to set/clear table bitmap wei.fang
2026-05-27 10:02 ` [PATCH net-next 7/9] net: dsa: netc: add VLAN filter table and egress treatment management wei.fang
2026-05-27 10:02 ` [PATCH net-next 8/9] net: dsa: netc: add bridge mode support wei.fang
2026-05-27 10:02 ` [PATCH net-next 9/9] net: dsa: netc: implement dynamic FDB entry aging wei.fang
2026-05-29  1:53 ` Wei Fang [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=DBBPR04MB7500385FABFC6DB0DF9792DF88162@DBBPR04MB7500.eurprd04.prod.outlook.com \
    --to=wei.fang@nxp$(echo .)com \
    --cc=andrew+netdev@lunn$(echo .)ch \
    --cc=andrew@lunn$(echo .)ch \
    --cc=chleroy@kernel$(echo .)org \
    --cc=claudiu.manoil@nxp$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=imx@lists$(echo .)linux.dev \
    --cc=kuba@kernel$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=olteanv@gmail$(echo .)com \
    --cc=pabeni@redhat$(echo .)com \
    --cc=vladimir.oltean@nxp$(echo .)com \
    --cc=wei.fang@oss$(echo .)nxp.com \
    --cc=xiaoning.wang@nxp$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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