[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <99d4c608-d821-7f87-48c1-aa1898441194@gmail.com>
Date: Wed, 27 Jan 2021 17:03:23 -0800
From: Florian Fainelli <f.fainelli@...il.com>
To: Vladimir Oltean <olteanv@...il.com>,
"David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org
Cc: Andrew Lunn <andrew@...n.ch>,
Vivien Didelot <vivien.didelot@...il.com>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>
Subject: Re: [PATCH net-next 0/4] Automatically manage DSA master interface
state
On 1/26/2021 5:00 PM, Vladimir Oltean wrote:
> From: Vladimir Oltean <vladimir.oltean@....com>
>
> This patch series adds code that makes DSA open the master interface
> automatically whenever one user interface gets opened, either by the
> user, or by various networking subsystems: netconsole, nfsroot.
> With that in place, we can remove some of the places in the network
> stack where DSA-specific code was sprinkled.
>
> Vladimir Oltean (4):
> net: dsa: automatically bring up DSA master when opening user port
> net: dsa: automatically bring user ports down when master goes down
> Revert "net: Have netpoll bring-up DSA management interface"
> Revert "net: ipv4: handle DSA enabled master network devices"
I really like all patches but number #2, though I don't believe there
are existing use cases besides you one you described where it makes
sense to keep a switch in an unmanaged mode being "headless" with its
CPU port down, while the user-facing ports are up.
--
Florian
Powered by blists - more mailing lists