Lines Matching full:lag
306 When using multiple CPU ports, it is possible to stack a LAG (bonding/team)
307 device between the DSA slave devices and the physical DSA masters. The LAG
308 device is thus also a DSA master, but the LAG slave devices continue to be DSA
310 recovery in case the LAG DSA master disappears). Thus, the data path of the LAG
313 LAG slave). Therefore, the RX data path of the LAG DSA master is not used.
315 ``dsa_enqueue_skb``, which calls ``dev_queue_xmit`` towards the LAG DSA master.
655 master->dsa_ptr``. Additionally, the master can also be a LAG device where
656 all the slave devices are physical DSA masters. LAG DSA masters also have a
658 duplicate of the first physical DSA master's (LAG slave) ``dsa_ptr``. In case
659 of a LAG DSA master, a further call to ``port_lag_join`` will be emitted
661 masters, requesting them to create a hardware LAG associated with the LAG
859 - ``DSA_DB_LAG``: the entry belongs to the address database of LAG ``db->lag``.
865 DSA associates each offloaded bridge and each offloaded LAG with a one-based ID
868 scheme (the ID is readable through ``db->bridge.num`` and ``db->lag.id`` or may
875 and ``db->lag.id`` are always set to 0 in that case (to denote the lack of
1029 DSA is capable of offloading a link aggregation group (LAG) to hardware that
1033 logical port at the moment. Due to this, events where a LAG joins/leaves a
1035 LAG join/leave the bridge. Switchdev port attributes (VLAN filtering, STP
1036 state, etc) and objects (VLANs, MDB entries) offloaded to a LAG as bridge port
1038 on all members of the LAG. Static bridge FDB entries on a LAG are not yet
1043 LAG. The driver may return ``-EOPNOTSUPP``, and in this case, DSA will fall
1046 - ``port_lag_leave``: function invoked when a given switch port leaves a LAG
1049 the LAG changes, and the hashing function needs rebalancing to only make use
1050 of the subset of physical LAG member ports that are up.
1052 Drivers that benefit from having an ID associated with each offloaded LAG
1054 method. The LAG ID associated with a bonding/team interface can then be