diff options
author | David S. Miller <davem@davemloft.net> | 2018-07-11 23:10:20 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2018-07-11 23:10:20 -0700 |
commit | d90a5215c8ff7f665336d404a56f26c320b9dd73 (patch) | |
tree | 65612105eca58cee46fa24ce4f5bee81ef05984b /fs/jffs2/fs.c | |
parent | 80fd2d6ca5461b2752744df2e6e387cc65e7b86c (diff) | |
parent | b5de82f3dfbebc2d1b6db72c68f119a1e0427ca8 (diff) |
Merge branch 'mlxsw-ERSPAN-Take-LACP-state-into-consideration'
Ido Schimmel says:
====================
mlxsw: ERSPAN: Take LACP state into consideration
Petr says:
When offloading mirror-to-gretap, mlxsw needs to preroute the path that
the encapsulated packet will take. That path may include a LAG device
above a front panel port. So far, mlxsw resolved the path to the first
up front panel slave of the LAG interface, but that only reflects
administrative state of the port. It neglects to consider whether the
port actually has a carrier, and what the LACP state is. This patch set
aims to address these problems.
Patch #1 publishes team_port_get_rcu().
Then in patch #2, a new function is introduced,
mlxsw_sp_port_dev_check(). That returns, for a given netdevice that is a
slave of a LAG device, whether that device is "txable", i.e. whether the
LAG master would send traffic through it. Since there's no good place to
put LAG-wide helpers, introduce a new header include/net/lag.h.
Finally in patch #3, fix the slave selection logic to take into
consideration whether a given slave has a carrier and whether it is
txable.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'fs/jffs2/fs.c')
0 files changed, 0 insertions, 0 deletions