[v3,net-next,4/8] net: dsa: implement auto-normalization of MTU for bridge hardware datapath
diff mbox series

Message ID 20200326224040.32014-5-olteanv@gmail.com
State Changes Requested
Delegated to: David Miller
Headers show
  • Configure the MTU on DSA switches
Related show

Commit Message

Vladimir Oltean March 26, 2020, 10:40 p.m. UTC
From: Vladimir Oltean <vladimir.oltean@nxp.com>

Many switches don't have an explicit knob for configuring the MTU
(maximum transmission unit per interface).  Instead, they do the
length-based packet admission checks on the ingress interface, for
reasons that are easy to understand (why would you accept a packet in
the queuing subsystem if you know you're going to drop it anyway).

So it is actually the MRU that these switches permit configuring.

In Linux there only exists the IFLA_MTU netlink attribute and the
associated dev_set_mtu function. The comments like to play blind and say
that it's changing the "maximum transfer unit", which is to say that
there isn't any directionality in the meaning of the MTU word. So that
is the interpretation that this patch is giving to things: MTU == MRU.

When 2 interfaces having different MTUs are bridged, the bridge driver
MTU auto-adjustment logic kicks in: what br_mtu_auto_adjust() does is it
adjusts the MTU of the bridge net device itself (and not that of the
slave net devices) to the minimum value of all slave interfaces, in
order for forwarded packets to not exceed the MTU regardless of the
interface they are received and send on.

The idea behind this behavior, and why the slave MTUs are not adjusted,
is that normal termination from Linux over the L2 forwarding domain
should happen over the bridge net device, which _is_ properly limited by
the minimum MTU. And termination over individual slave devices is
possible even if those are bridged. But that is not "forwarding", so
there's no reason to do normalization there, since only a single
interface sees that packet.

The problem with those switches that can only control the MRU is with
the offloaded data path, where a packet received on an interface with
MRU 9000 would still be forwarded to an interface with MRU 1500. And the
br_mtu_auto_adjust() function does not really help, since the MTU
configured on the bridge net device is ignored.

In order to enforce the de-facto MTU == MRU rule for these switches, we
need to do MTU normalization, which means: in order for no packet larger
than the MTU configured on this port to be sent, then we need to limit
the MRU on all ports that this packet could possibly come from. AKA
since we are configuring the MRU via MTU, it means that all ports within
a bridge forwarding domain should have the same MTU.

And that is exactly what this patch is trying to do.

From an implementation perspective, we try to follow the intent of the
user, otherwise there is a risk that we might livelock them (they try to
change the MTU on an already-bridged interface, but we just keep
changing it back in an attempt to keep the MTU normalized). So the MTU
that the bridge is normalized to is either:

 - The most recently changed one:

   ip link set dev swp0 master br0
   ip link set dev swp1 master br0
   ip link set dev swp0 mtu 1400

   This sequence will make swp1 inherit MTU 1400 from swp0.

 - The one of the most recently added interface to the bridge:

   ip link set dev swp0 master br0
   ip link set dev swp1 mtu 1400
   ip link set dev swp1 master br0

   The above sequence will make swp0 inherit MTU 1400 as well.

Suggested-by: Florian Fainelli <f.fainelli@gmail.com>
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Changes in v3:
Moved the implementation to the DSA core (it was in the bridge driver
Added a variable by which drivers should denote if they require this
behavior or not.

Changes in v2:
Patch is new.

 include/net/dsa.h  |   6 +++
 net/dsa/dsa2.c     |   2 +-
 net/dsa/dsa_priv.h |   4 ++
 net/dsa/slave.c    | 114 +++++++++++++++++++++++++++++++++++++++++++++
 4 files changed, 125 insertions(+), 1 deletion(-)


kbuild test robot April 2, 2020, 1:25 a.m. UTC | #1
Hi Vladimir,

I love your patch! Perhaps something to improve:

[auto build test WARNING on net-next/master]
[also build test WARNING on linus/master v5.6-rc7 next-20200327]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Vladimir-Oltean/Configure-the-MTU-on-DSA-switches/20200327-094801
base:   https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 92b7e62e5630a370955a4760bbeb3967457034ec
        # apt-get install sparse
        # sparse version: v0.6.1-187-gbff9b106-dirty
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
:::::: branch date: 17 hours ago
:::::: commit date: 17 hours ago

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

   net/dsa/slave.c:506:13: sparse: sparse: incorrect type in initializer (different address spaces) @@    expected void const [noderef] <asn:3> *__vpp_verify @@    got const [noderef] <asn:3> *__vpp_verify @@
   net/dsa/slave.c:506:13: sparse:    expected void const [noderef] <asn:3> *__vpp_verify
   net/dsa/slave.c:506:13: sparse:    got struct pcpu_sw_netstats *
   net/dsa/slave.c:640:21: sparse: sparse: incorrect type in initializer (different address spaces) @@    expected void const [noderef] <asn:3> *__vpp_verify @@    got const [noderef] <asn:3> *__vpp_verify @@
   net/dsa/slave.c:640:21: sparse:    expected void const [noderef] <asn:3> *__vpp_verify
   net/dsa/slave.c:640:21: sparse:    got struct pcpu_sw_netstats *
   net/dsa/slave.c:1106:21: sparse: sparse: incorrect type in initializer (different address spaces) @@    expected void const [noderef] <asn:3> *__vpp_verify @@    got const [noderef] <asn:3> *__vpp_verify @@
   net/dsa/slave.c:1106:21: sparse:    expected void const [noderef] <asn:3> *__vpp_verify
   net/dsa/slave.c:1106:21: sparse:    got struct pcpu_sw_netstats *
>> net/dsa/slave.c:1264:6: sparse: sparse: symbol 'dsa_bridge_mtu_normalization' was not declared. Should it be static?
   net/dsa/slave.c:1682:20: sparse: sparse: incorrect type in assignment (different address spaces) @@    expected struct pcpu_sw_netstats *stats64 @@    got struct pcpu_sw_netstruct pcpu_sw_netstats *stats64 @@
   net/dsa/slave.c:1682:20: sparse:    expected struct pcpu_sw_netstats *stats64
   net/dsa/slave.c:1682:20: sparse:    got struct pcpu_sw_netstats [noderef] <asn:3> *pcpu_stats
   net/dsa/slave.c:1726:22: sparse: sparse: incorrect type in argument 1 (different address spaces) @@    expected void [noderef] <asn:3> *__pdata @@    got svoid [noderef] <asn:3> *__pdata @@
   net/dsa/slave.c:1726:22: sparse:    expected void [noderef] <asn:3> *__pdata
   net/dsa/slave.c:1726:22: sparse:    got struct pcpu_sw_netstats *stats64
   net/dsa/slave.c:1745:22: sparse: sparse: incorrect type in argument 1 (different address spaces) @@    expected void [noderef] <asn:3> *__pdata @@    got svoid [noderef] <asn:3> *__pdata @@
   net/dsa/slave.c:1745:22: sparse:    expected void [noderef] <asn:3> *__pdata
   net/dsa/slave.c:1745:22: sparse:    got struct pcpu_sw_netstats *stats64

Please review and possibly fold the followup patch.

0-DAY CI Kernel Test Service, Intel Corporation

diff mbox series

diff --git a/include/net/dsa.h b/include/net/dsa.h
index 1bb1e0852e31..0f4e55543cf8 100644
--- a/include/net/dsa.h
+++ b/include/net/dsa.h
@@ -284,6 +284,12 @@  struct dsa_switch {
 	bool			pcs_poll;
+	/* For switches that only have the MRU configurable. To ensure the
+	 * configured MTU is not exceeded, normalization of MRU on all bridged
+	 * interfaces is needed.
+	 */
+	bool			mtu_enforcement_ingress;
 	size_t num_ports;
diff --git a/net/dsa/dsa2.c b/net/dsa/dsa2.c
index e7c30b472034..9a271a58a41d 100644
--- a/net/dsa/dsa2.c
+++ b/net/dsa/dsa2.c
@@ -18,8 +18,8 @@ 
 #include "dsa_priv.h"
-static LIST_HEAD(dsa_tree_list);
 static DEFINE_MUTEX(dsa2_mutex);
 static const struct devlink_ops dsa_devlink_ops = {
diff --git a/net/dsa/dsa_priv.h b/net/dsa/dsa_priv.h
index da3be60beefe..904cc7c9b882 100644
--- a/net/dsa/dsa_priv.h
+++ b/net/dsa/dsa_priv.h
@@ -194,4 +194,8 @@  dsa_slave_to_master(const struct net_device *dev)
 /* switch.c */
 int dsa_switch_register_notifier(struct dsa_switch *ds);
 void dsa_switch_unregister_notifier(struct dsa_switch *ds);
+/* dsa2.c */
+extern struct list_head dsa_tree_list;
diff --git a/net/dsa/slave.c b/net/dsa/slave.c
index 1a99bbab0722..8ced165a7908 100644
--- a/net/dsa/slave.c
+++ b/net/dsa/slave.c
@@ -1218,6 +1218,116 @@  static int dsa_slave_vlan_rx_kill_vid(struct net_device *dev, __be16 proto,
 	return dsa_port_vid_del(dp, vid);
+struct dsa_hw_port {
+	struct list_head list;
+	struct net_device *dev;
+	int old_mtu;
+static int dsa_hw_port_list_set_mtu(struct list_head *hw_port_list, int mtu)
+	const struct dsa_hw_port *p;
+	int err;
+	list_for_each_entry(p, hw_port_list, list) {
+		if (p->dev->mtu == mtu)
+			continue;
+		err = dev_set_mtu(p->dev, mtu);
+		if (err)
+			goto rollback;
+	}
+	return 0;
+	list_for_each_entry_continue_reverse(p, hw_port_list, list) {
+		if (p->dev->mtu == p->old_mtu)
+			continue;
+		if (dev_set_mtu(p->dev, p->old_mtu))
+			netdev_err(p->dev, "Failed to restore MTU\n");
+	}
+	return err;
+static void dsa_hw_port_list_free(struct list_head *hw_port_list)
+	struct dsa_hw_port *p, *n;
+	list_for_each_entry_safe(p, n, hw_port_list, list)
+		kfree(p);
+/* Make the hardware datapath to/from @dev limited to a common MTU */
+void dsa_bridge_mtu_normalization(struct dsa_port *dp)
+	struct list_head hw_port_list;
+	struct dsa_switch_tree *dst;
+	int min_mtu = ETH_MAX_MTU;
+	struct dsa_port *other_dp;
+	int err;
+	if (!dp->ds->mtu_enforcement_ingress)
+		return;
+	if (!dp->bridge_dev)
+		return;
+	INIT_LIST_HEAD(&hw_port_list);
+	/* Populate the list of ports that are part of the same bridge
+	 * as the newly added/modified port
+	 */
+	list_for_each_entry(dst, &dsa_tree_list, list) {
+		list_for_each_entry(other_dp, &dst->ports, list) {
+			struct dsa_hw_port *hw_port;
+			struct net_device *slave;
+			if (other_dp->type != DSA_PORT_TYPE_USER)
+				continue;
+			if (other_dp->bridge_dev != dp->bridge_dev)
+				continue;
+			if (!other_dp->ds->mtu_enforcement_ingress)
+				continue;
+			slave = other_dp->slave;
+			if (min_mtu > slave->mtu)
+				min_mtu = slave->mtu;
+			hw_port = kzalloc(sizeof(*hw_port), GFP_KERNEL);
+			if (!hw_port)
+				goto out;
+			hw_port->dev = slave;
+			hw_port->old_mtu = slave->mtu;
+			list_add(&hw_port->list, &hw_port_list);
+		}
+	}
+	/* Attempt to configure the entire hardware bridge to the newly added
+	 * interface's MTU first, regardless of whether the intention of the
+	 * user was to raise or lower it.
+	 */
+	err = dsa_hw_port_list_set_mtu(&hw_port_list, dp->slave->mtu);
+	if (!err)
+		goto out;
+	/* Clearly that didn't work out so well, so just set the minimum MTU on
+	 * all hardware bridge ports now. If this fails too, then all ports will
+	 * still have their old MTU rolled back anyway.
+	 */
+	dsa_hw_port_list_set_mtu(&hw_port_list, min_mtu);
+	dsa_hw_port_list_free(&hw_port_list);
 static int dsa_slave_change_mtu(struct net_device *dev, int new_mtu)
 	struct net_device *master = dsa_slave_to_master(dev);
@@ -1294,6 +1404,8 @@  static int dsa_slave_change_mtu(struct net_device *dev, int new_mtu)
 	dev->mtu = new_mtu;
+	dsa_bridge_mtu_normalization(dp);
 	return 0;
@@ -1648,6 +1760,8 @@  static int dsa_slave_changeupper(struct net_device *dev,
 	if (netif_is_bridge_master(info->upper_dev)) {
 		if (info->linking) {
 			err = dsa_port_bridge_join(dp, info->upper_dev);
+			if (!err)
+				dsa_bridge_mtu_normalization(dp);
 			err = notifier_from_errno(err);
 		} else {
 			dsa_port_bridge_leave(dp, info->upper_dev);