1. 24 3月, 2017 1 次提交
  2. 07 2月, 2017 1 次提交
  3. 04 12月, 2016 1 次提交
    • I
      mlxsw: core: Create an ordered workqueue for FIB offload · a3832b31
      Ido Schimmel 提交于
      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: NIdo Schimmel <idosch@mellanox.com>
      Signed-off-by: NJiri Pirko <jiri@mellanox.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      a3832b31
  4. 30 11月, 2016 2 次提交
  5. 26 11月, 2016 3 次提交
  6. 22 11月, 2016 1 次提交
  7. 17 11月, 2016 2 次提交
  8. 31 10月, 2016 3 次提交
  9. 29 10月, 2016 1 次提交
  10. 24 10月, 2016 1 次提交
  11. 21 9月, 2016 1 次提交
  12. 25 7月, 2016 1 次提交
  13. 13 7月, 2016 1 次提交
  14. 10 6月, 2016 1 次提交
    • B
      mlxsw: core: Remove deprecated create_workqueue · 3d5479e9
      Bhaktipriya Shridhar 提交于
      alloc_workqueue replaces deprecated create_workqueue().
      
      A dedicated workqueue has been used since the workqueue
      mlxsw_wq is used for FDB notif. processing with workitems that are
      involved in normal device operation && because it's a network device
      which can be depended upon during memory reclaim.
      
      Workitems &trans->timeout_dw and &mlxsw_sp->fdb_notify.dw,
      map to mlxsw_sp_fdb_notify_work (processes FDB notifications from the
      underlying device and resolves the netdev to which the entry points to
      and notifies the bridge using the switchdev notifier) and
      mlxsw_emad_trans_timeout_work (provides async EMAD register access)
      respectively. They require forward progress under memory pressure and
      hence, WQ_MEM_RECLAIM has been set.
      
      Since there are only a fixed number of work items, explicit concurrency
      limit is unnecessary here.
      Signed-off-by: NBhaktipriya Shridhar <bhaktipriya96@gmail.com>
      Tested-by: NIdo Schimmel <idosch@mellanox.com>
      Acked-by: NJiri Pirko <jiri@mellanox.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      3d5479e9
  15. 15 4月, 2016 4 次提交
  16. 09 4月, 2016 3 次提交
  17. 02 3月, 2016 2 次提交
  18. 23 12月, 2015 1 次提交
  19. 04 12月, 2015 1 次提交
  20. 01 12月, 2015 1 次提交
  21. 30 10月, 2015 1 次提交
  22. 16 10月, 2015 2 次提交
  23. 15 10月, 2015 1 次提交
  24. 28 8月, 2015 2 次提交
  25. 10 8月, 2015 2 次提交