1. 17 8月, 2016 5 次提交
  2. 14 8月, 2016 6 次提交
  3. 26 7月, 2016 2 次提交
  4. 15 7月, 2016 2 次提交
  5. 05 7月, 2016 3 次提交
  6. 03 7月, 2016 2 次提交
  7. 01 7月, 2016 1 次提交
  8. 27 6月, 2016 3 次提交
  9. 23 6月, 2016 4 次提交
  10. 10 6月, 2016 5 次提交
  11. 07 6月, 2016 1 次提交
  12. 18 5月, 2016 1 次提交
    • M
      net/mlx5_core: Use tasklet for user-space CQ completion events · 94c6825e
      Matan Barak 提交于
      Previously, we've fired all our completion callbacks straight from
      our ISR.
      
      Some of those callbacks were lightweight (for example, mlx5 Ethernet
      napi callbacks), but some of them did more work (for example,
      the user-space RDMA stack uverbs' completion handler). Besides that,
      doing more than the minimal work in ISR is generally considered wrong,
      it could even lead to a hard lockup of the system. Since when a lot
      of completion events are generated by the hardware, the loop over
      those events could be so long, that we'll get into a hard lockup by
      the system watchdog.
      
      In order to avoid that, add a new way of invoking completion events
      callbacks. In the interrupt itself, we add the CQs which receive
      completion event to a per-EQ list and schedule a tasklet. In the
      tasklet context we loop over all the CQs in the list and invoke the
      user callback.
      Signed-off-by: NMatan Barak <matanb@mellanox.com>
      Signed-off-by: NDoug Ledford <dledford@redhat.com>
      94c6825e
  13. 17 5月, 2016 3 次提交
  14. 13 5月, 2016 2 次提交