Lines Matching full:lag

310 When using multiple CPU ports, it is possible to stack a LAG (bonding/team)
311 device between the DSA user devices and the physical DSA conduits. The LAG
312 device is thus also a DSA conduit, but the LAG slave devices continue to be DSA
314 recovery in case the LAG DSA conduit disappears). Thus, the data path of the LAG
317 LAG slave). Therefore, the RX data path of the LAG DSA conduit is not used.
319 ``dsa_enqueue_skb``, which calls ``dev_queue_xmit`` towards the LAG DSA conduit.
659   conduit->dsa_ptr``. Additionally, the conduit can also be a LAG device where
660   all the slave devices are physical DSA conduits. LAG DSA  also have a
662   duplicate of the first physical DSA conduit's (LAG slave) ``dsa_ptr``. In case
663   of a LAG DSA conduit, a further call to ``port_lag_join`` will be emitted
665   conduits, requesting them to create a hardware LAG associated with the LAG
863 - ``DSA_DB_LAG``: the entry belongs to the address database of LAG ``db->lag``.
869 DSA associates each offloaded bridge and each offloaded LAG with a one-based ID
872 scheme (the ID is readable through ``db->bridge.num`` and ``db->lag.id`` or may
879 and ``db->lag.id`` are always set to 0 in that case (to denote the lack of
1033 DSA is capable of offloading a link aggregation group (LAG) to hardware that
1037 logical port at the moment. Due to this, events where a LAG joins/leaves a
1039 LAG join/leave the bridge. Switchdev port attributes (VLAN filtering, STP
1040 state, etc) and objects (VLANs, MDB entries) offloaded to a LAG as bridge port
1042 on all members of the LAG. Static bridge FDB entries on a LAG are not yet
1047   LAG. The driver may return ``-EOPNOTSUPP``, and in this case, DSA will fall
1050 - ``port_lag_leave``: function invoked when a given switch port leaves a LAG
1053   the LAG changes, and the hashing function needs rebalancing to only make use
1054   of the subset of physical LAG member ports that are up.
1056 Drivers that benefit from having an ID associated with each offloaded LAG
1058 method. The LAG ID associated with a bonding/team interface can then be