Netdev Archive on
help / color / mirror / Atom feed
From: Vladimir Oltean <>
To: Grygorii Strashko <>
Cc: Arnd Bergmann <>,
	Networking <>,
	Jakub Kicinski <>,
	"David S. Miller" <>,
	Naresh Kamboju <>,
	Lars Povlsen <>,
	Steen Hegelund <>,
	Microchip Linux Driver Support <>,
	Florian Fainelli <>,
	Andrew Lunn <>,
	Vivien Didelot <>,
	Ido Schimmel <>, Jiri Pirko <>,
	Roopa Prabhu <>,
	Nikolay Aleksandrov <>,
	Linux Kernel Functional Testing <>,
	Vignesh Raghavendra <>
Subject: Re: [PATCH net-next] net: build all switchdev drivers as modules when the bridge is a module
Date: Tue, 3 Aug 2021 11:58:19 +0000	[thread overview]
Message-ID: <20210803115819.sdtdqhmfk5k4olip@skbuf> (raw)
In-Reply-To: <>

On Tue, Aug 03, 2021 at 02:18:38PM +0300, Grygorii Strashko wrote:
> In my opinion, the problem is a bit bigger here than just fixing the build :(
> In case, of ^cpsw the switchdev mode is kinda optional and in many cases
> (especially for testing purposes, NFS) the multi-mac mode is still preferable mode.
> There were no such tight dependency between switchdev drivers and bridge core before and switchdev serviced as
> independent, notification based layer between them, so ^cpsw still can be "Y" and bridge can be "M".
> Now for mostly every kernel build configuration the CONFIG_BRIDGE will need to be set as "Y", or we will have
> to update drivers to support build with BRIDGE=n and maintain separate builds for networking vs non-networking testing.
> But is this enough? Wouldn't it cause 'chain reaction' required to add more and more "Y" options (like CONFIG_VLAN_8021Q)?
> PS. Just to be sure we on the same page - ARM builds will be forced (with this patch) to have CONFIG_TI_CPSW_SWITCHDEV=m
> and so all our automation testing will just fail with omap2plus_defconfig.

I didn't realize it is such a big use case to have the bridge built as
module and cpsw as built-in. I will send a patch that converts the
switchdev_bridge_port_{,un}offload functions to simply emit a blocking
switchdev notifier which the bridge processes (a la SWITCHDEV_FDB_ADD_TO_BRIDGE),
therefore making switchdev and the bridge loosely coupled in order to
keep your setup the way it was before.

  reply	other threads:[~2021-08-03 11:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-26 14:25 Vladimir Oltean
2021-07-27 10:15 ` Anders Roxell
2021-07-27 10:20 ` patchwork-bot+netdevbpf
2021-08-02 14:47 ` Arnd Bergmann
2021-08-03 11:18   ` Grygorii Strashko
2021-08-03 11:58     ` Vladimir Oltean [this message]
2021-08-03 12:33       ` Arnd Bergmann
2021-08-03 12:46         ` Grygorii Strashko

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210803115819.sdtdqhmfk5k4olip@skbuf \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH net-next] net: build all switchdev drivers as modules when the bridge is a module' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).