Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1615949 > unrolled thread

[PATCH net-next] net: stmmac: allow changing the MTU while the interface is running

Started byNiklas Cassel <niklas.cassel@axis.com>
First post2017-04-04 14:20 +0200
Last post2017-04-05 17:00 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH net-next] net: stmmac: allow changing the MTU while the interface is running Niklas Cassel <niklas.cassel@axis.com> - 2017-04-04 14:20 +0200
    Re: [PATCH net-next] net: stmmac: allow changing the MTU while the  interface is running David Miller <davem@davemloft.net> - 2017-04-05 17:00 +0200

#1615949 — [PATCH net-next] net: stmmac: allow changing the MTU while the interface is running

FromNiklas Cassel <niklas.cassel@axis.com>
Date2017-04-04 14:20 +0200
Subject[PATCH net-next] net: stmmac: allow changing the MTU while the interface is running
Message-ID<tsvBg-4KM-15@gated-at.bofh.it>
From: Niklas Cassel <niklas.cassel@axis.com>

Setting ethtool ops for stmmac is only allowed when the interface is up.
Setting MTU (a netdev op) for stmmac is only allowed when the interface
is down.

It seems that the only reason why MTU cannot be changed when running is
that we have not bothered to implement a nice way to dealloc/alloc the
descriptor rings.

To make it less confusing for the user, call ndo_stop() and ndo_open()
from ndo_change_mtu(). This is not a nice way to dealloc/alloc the
descriptor rings, since it will announce that the interface is being
brought down/up to user space, but there are several other drivers doing
it this way, and it is arguably better than just returning -EBUSY.

Signed-off-by: Niklas Cassel <niklas.cassel@axis.com>
---
 drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 12 +++++-------
 1 file changed, 5 insertions(+), 7 deletions(-)

diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
index c1c63197ff73..fd268dc0df02 100644
--- a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
+++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
@@ -3109,17 +3109,15 @@ static void stmmac_set_rx_mode(struct net_device *dev)
  */
 static int stmmac_change_mtu(struct net_device *dev, int new_mtu)
 {
-	struct stmmac_priv *priv = netdev_priv(dev);
-
-	if (netif_running(dev)) {
-		netdev_err(priv->dev, "must be stopped to change its MTU\n");
-		return -EBUSY;
-	}
-
 	dev->mtu = new_mtu;
 
 	netdev_update_features(dev);
 
+	if (netif_running(dev)) {
+		stmmac_release(dev);
+		stmmac_open(dev);
+	}
+
 	return 0;
 }
 
-- 
2.11.0

[toc] | [next] | [standalone]


#1617024 — Re: [PATCH net-next] net: stmmac: allow changing the MTU while the interface is running

FromDavid Miller <davem@davemloft.net>
Date2017-04-05 17:00 +0200
SubjectRe: [PATCH net-next] net: stmmac: allow changing the MTU while the interface is running
Message-ID<tsUzD-3Vt-11@gated-at.bofh.it>
In reply to#1615949
From: Niklas Cassel <niklas.cassel@axis.com>
Date: Tue, 4 Apr 2017 14:18:54 +0200

> From: Niklas Cassel <niklas.cassel@axis.com>
> 
> Setting ethtool ops for stmmac is only allowed when the interface is up.
> Setting MTU (a netdev op) for stmmac is only allowed when the interface
> is down.
> 
> It seems that the only reason why MTU cannot be changed when running is
> that we have not bothered to implement a nice way to dealloc/alloc the
> descriptor rings.
> 
> To make it less confusing for the user, call ndo_stop() and ndo_open()
> from ndo_change_mtu(). This is not a nice way to dealloc/alloc the
> descriptor rings, since it will announce that the interface is being
> brought down/up to user space, but there are several other drivers doing
> it this way, and it is arguably better than just returning -EBUSY.
> 
> Signed-off-by: Niklas Cassel <niklas.cassel@axis.com>

You can't do this with no error handling.

Instead, you must do this using a "prepare", "commit" sequence.
First making sure you can reallocate all necessary resources,
and make the config change, before actually doing so.

You're not even checking if the re-open fails, meaning that an MTU
change can cause the interface to shut down.  That is simply not
acceptable.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web