An error occurred fetching the project authors.
  1. 08 Feb, 2019 1 commit
  2. 18 Dec, 2018 1 commit
    • Shalom Toledo's avatar
      mlxsw: core: Increase timeout during firmware flash process · cf0b70e7
      Shalom Toledo authored
      During the firmware flash process, some of the EMADs get timed out, which
      causes the driver to send them again with a limit of 5 retries. There are
      some situations in which 5 retries is not enough and the EMAD access fails.
      If the failed EMAD was related to the flashing process, the driver fails
      the flashing.
      
      The reason for these timeouts during firmware flashing is cache misses in
      the CPU running the firmware. In case the CPU needs to fetch instructions
      from the flash when a firmware is flashed, it needs to wait for the
      flashing to complete. Since flashing takes time, it is possible for pending
      EMADs to timeout.
      
      Fix by increasing EMADs' timeout while flashing firmware.
      
      Fixes: ce6ef68f ("mlxsw: spectrum: Implement the ethtool flash_device callback")
      Signed-off-by: default avatarShalom Toledo <shalomt@mellanox.com>
      Signed-off-by: default avatarIdo Schimmel <idosch@mellanox.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      cf0b70e7
  3. 03 Dec, 2018 1 commit
  4. 18 Oct, 2018 1 commit
  5. 09 Aug, 2018 2 commits
  6. 05 Jun, 2018 1 commit
  7. 29 May, 2018 1 commit
  8. 19 May, 2018 2 commits
  9. 01 Apr, 2018 4 commits
  10. 16 Jan, 2018 4 commits
  11. 25 May, 2017 1 commit
  12. 24 Mar, 2017 1 commit
  13. 06 Feb, 2017 1 commit
  14. 04 Dec, 2016 1 commit
    • Ido Schimmel's avatar
      mlxsw: core: Create an ordered workqueue for FIB offload · a3832b31
      Ido Schimmel authored
      We're going to start processing FIB entries addition / deletion events
      in deferred work. These work items must be processed in the order they
      were submitted or otherwise we can have differences between the kernel's
      FIB table and the device's.
      
      Solve this by creating an ordered workqueue to which these work items
      will be submitted to. Note that we can't simply convert the current
      workqueue to be ordered, as EMADs re-transmissions are also processed in
      deferred work.
      
      Later on, we can migrate other work items to this workqueue, such as FDB
      notification processing and nexthop resolution, since they all take the
      same lock anyway.
      Signed-off-by: default avatarIdo Schimmel <idosch@mellanox.com>
      Signed-off-by: default avatarJiri Pirko <jiri@mellanox.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      a3832b31
  15. 26 Nov, 2016 6 commits
  16. 22 Nov, 2016 1 commit
  17. 17 Nov, 2016 1 commit
  18. 30 Oct, 2016 3 commits
  19. 28 Oct, 2016 1 commit
  20. 23 Oct, 2016 1 commit
  21. 21 Sep, 2016 5 commits