1. 02 6月, 2020 2 次提交
  2. 10 5月, 2020 4 次提交
  3. 28 4月, 2020 7 次提交
  4. 31 3月, 2020 4 次提交
  5. 27 3月, 2020 1 次提交
  6. 20 3月, 2020 1 次提交
  7. 19 3月, 2020 1 次提交
  8. 09 3月, 2020 1 次提交
  9. 06 3月, 2020 2 次提交
  10. 27 2月, 2020 1 次提交
  11. 26 2月, 2020 2 次提交
  12. 25 2月, 2020 3 次提交
  13. 24 2月, 2020 1 次提交
  14. 23 2月, 2020 2 次提交
    • I
      mlxsw: spectrum_router: Take router lock from netdev listener · b43c12e7
      Ido Schimmel 提交于
      One entry point into the routing code is from the netdev listener block.
      Some netdev events require access to internal router structures. For
      example, changing the MTU of a netdev requires looking-up the backing
      RIF and adjusting its MTU.
      
      In order to serialize access to shared router structures, take the
      router lock when processing netdev events that require access to it.
      Signed-off-by: NIdo Schimmel <idosch@mellanox.com>
      Acked-by: NJiri Pirko <jiri@mellanox.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      b43c12e7
    • I
      mlxsw: spectrum_router: Store NVE decapsulation configuration in router · 8e18d85e
      Ido Schimmel 提交于
      When a host route is added, the driver checks if the route needs to be
      promoted to perform NVE decapsulation based on the current NVE
      configuration. If so, the index of the decapsulation entry is retrieved
      and associated with the route.
      
      Currently, this information is stored in the NVE module which the router
      module consults. Since the information is protected under RTNL and since
      route insertion happens with RTNL held, there is no problem to retrieve
      the information from the NVE module.
      
      However, this is going to change and route insertion will no longer
      happen under RTNL. Instead, a dedicated lock will be introduced for the
      router module.
      
      Therefore, store this information in the router module and change the
      router module to consult this copy.
      
      The validity of the information is set / cleared whenever an NVE tunnel
      is initialized / de-initialized. When this happens the NVE module calls
      into the router module to promote / demote the relevant host route.
      Signed-off-by: NIdo Schimmel <idosch@mellanox.com>
      Acked-by: NJiri Pirko <jiri@mellanox.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      8e18d85e
  15. 21 2月, 2020 3 次提交
  16. 18 2月, 2020 1 次提交
  17. 25 1月, 2020 3 次提交
  18. 20 1月, 2020 1 次提交