[Bridge] [PATCH v6 net-next 0/7] Let switchdev drivers offload and unoffload bridge ports at their own convenience

patchwork-bot+netdevbpf at kernel.org patchwork-bot+netdevbpf at kernel.org
Thu Jul 22 07:40:05 UTC 2021


This series was applied to netdev/net-next.git (refs/heads/master):

On Wed, 21 Jul 2021 19:23:56 +0300 you wrote:
> This series introduces an explicit API through which switchdev drivers
> mark a bridge port as offloaded or not:
> - switchdev_bridge_port_offload()
> - switchdev_bridge_port_unoffload()
> Currently, the bridge assumes that a port is offloaded if
> dev_get_port_parent_id(dev, &ppid, recurse=true) returns something, but
> that is just an assumption that breaks some use cases (like a
> non-offloaded LAG interface on top of a switchdev port, bridged with
> other switchdev ports).
> [...]

Here is the summary with links:
  - [v6,net-next,1/7] net: dpaa2-switch: use extack in dpaa2_switch_port_bridge_join
  - [v6,net-next,2/7] net: dpaa2-switch: refactor prechangeupper sanity checks
  - [v6,net-next,3/7] net: bridge: disambiguate offload_fwd_mark
  - [v6,net-next,4/7] net: bridge: switchdev: recycle unused hwdoms
  - [v6,net-next,5/7] net: bridge: switchdev: let drivers inform which bridge ports are offloaded
  - [v6,net-next,6/7] net: bridge: guard the switchdev replay helpers against a NULL notifier block
  - [v6,net-next,7/7] net: bridge: move the switchdev object replay helpers to "push" mode

You are awesome, thank you!
Deet-doot-dot, I am a bot.

More information about the Bridge mailing list