1. 04 5月, 2019 2 次提交
  2. 22 4月, 2019 1 次提交
  3. 19 4月, 2019 2 次提交
    • A
      mlxsw: spectrum: Fix autoneg status in ethtool · 151f0ddd
      Amit Cohen 提交于
      If link is down and autoneg is set to on/off, the status in ethtool does
      not change.
      
      The reason is when the link is down the function returns with zero
      before changing autoneg value.
      
      Move the checking of link state (up/down) to be performed after setting
      autoneg value, in order to be sure that autoneg will change in any case.
      
      Fixes: 56ade8fe ("mlxsw: spectrum: Add initial support for Spectrum ASIC")
      Signed-off-by: NAmit Cohen <amitc@mellanox.com>
      Signed-off-by: NIdo Schimmel <idosch@mellanox.com>
      Acked-by: NJiri Pirko <jiri@mellanox.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      151f0ddd
    • P
      mlxsw: spectrum: Put MC TCs into DWRR mode · f476b3f8
      Petr Machata 提交于
      Both Spectrum-1 and Spectrum-2 chips are currently configured such that
      pairs of TC n (which is used for UC traffic) and TC n+8 (which is used
      for MC traffic) are feeding into the same subgroup. Strict
      prioritization is configured between the two TCs, and by enabling
      MC-aware mode on the switch, the lower-numbered (UC) TCs are favored
      over the higher-numbered (MC) TCs.
      
      On Spectrum-2 however, there is an issue in configuration of the
      MC-aware mode. As a result, MC traffic is prioritized over UC traffic.
      To work around the issue, configure the MC TCs with DWRR mode (while
      keeping the UC TCs in strict mode).
      
      With this patch, the multicast-unicast arbitration results in the same
      behavior on both Spectrum-1 and Spectrum-2 chips.
      
      Fixes: 7b819530 ("mlxsw: spectrum: Configure MC-aware mode on mlxsw ports")
      Signed-off-by: NPetr Machata <petrm@mellanox.com>
      Signed-off-by: NIdo Schimmel <idosch@mellanox.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      f476b3f8
  4. 05 4月, 2019 2 次提交
  5. 29 3月, 2019 2 次提交
  6. 25 3月, 2019 1 次提交
  7. 04 3月, 2019 1 次提交
  8. 28 2月, 2019 1 次提交
  9. 27 2月, 2019 1 次提交
  10. 24 2月, 2019 8 次提交
  11. 22 2月, 2019 2 次提交
  12. 19 2月, 2019 1 次提交
  13. 18 2月, 2019 1 次提交
  14. 14 2月, 2019 1 次提交
  15. 13 2月, 2019 1 次提交
  16. 09 2月, 2019 1 次提交
  17. 07 2月, 2019 1 次提交
  18. 21 1月, 2019 1 次提交
  19. 09 1月, 2019 1 次提交
  20. 25 12月, 2018 1 次提交
  21. 21 12月, 2018 7 次提交
  22. 20 12月, 2018 1 次提交
    • I
      mlxsw: spectrum_router: Make RIF deletion more robust · 965fa8e6
      Ido Schimmel 提交于
      In the past we had multiple instances where RIFs were not properly
      deleted.
      
      One of the reasons for leaking a RIF was that at the time when IP
      addresses were flushed from the respective netdev (prompting the
      destruction of the RIF), the netdev was no longer a mlxsw upper. This
      caused the inet{,6}addr notification blocks to ignore the NETDEV_DOWN
      event and leak the RIF.
      
      Instead of checking whether the netdev is our upper when an IP address
      is removed, we can instead check if the netdev has a RIF configured.
      
      To look up a RIF we need to access mlxsw private data, so the patch
      stores the notification blocks inside a mlxsw struct. This then allows
      us to use container_of() and extract the required private data.
      Signed-off-by: NIdo Schimmel <idosch@mellanox.com>
      Reviewed-by: NPetr Machata <petrm@mellanox.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      965fa8e6