net: dsa: Rename IFLA_DSA_MASTER to IFLA_DSA_CONDUIT
This preserves the existing IFLA_DSA_MASTER which is part of the uAPI and creates an alias named IFLA_DSA_CONDUIT. Reviewed-by: Andrew Lunn <andrew@lunn.ch> Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com> Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com> Link: https://lore.kernel.org/r/20231023181729.1191071-3-florian.fainelli@broadcom.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
This commit is contained in:
committed by
Jakub Kicinski
parent
6ca80638b9
commit
87cd83714f
@@ -393,7 +393,7 @@ description which has an ``ethernet`` property. It is up to the user to
|
||||
configure the system for the switch to use other conduits.
|
||||
|
||||
DSA uses the ``rtnl_link_ops`` mechanism (with a "dsa" ``kind``) to allow
|
||||
changing the DSA conduit of a user port. The ``IFLA_DSA_MASTER`` u32 netlink
|
||||
changing the DSA conduit of a user port. The ``IFLA_DSA_CONDUIT`` u32 netlink
|
||||
attribute contains the ifindex of the conduit device that handles each user
|
||||
device. The DSA conduit must be a valid candidate based on firmware node
|
||||
information, or a LAG interface which contains only slaves which are valid
|
||||
@@ -435,7 +435,7 @@ Using iproute2, the following manipulations are possible:
|
||||
dsa master bond0
|
||||
|
||||
Notice that in the case of CPU ports under a LAG, the use of the
|
||||
``IFLA_DSA_MASTER`` netlink attribute is not strictly needed, but rather, DSA
|
||||
``IFLA_DSA_CONDUIT`` netlink attribute is not strictly needed, but rather, DSA
|
||||
reacts to the ``IFLA_MASTER`` attribute change of its present conduit (``eth0``)
|
||||
and migrates all user ports to the new upper of ``eth0``, ``bond0``. Similarly,
|
||||
when ``bond0`` is destroyed using ``RTM_DELLINK``, DSA migrates the user ports
|
||||
|
||||
Reference in New Issue
Block a user