1. 10 3月, 2016 1 次提交
  2. 03 2月, 2016 2 次提交
  3. 22 1月, 2016 3 次提交
  4. 20 1月, 2016 3 次提交
  5. 12 1月, 2016 1 次提交
  6. 24 12月, 2015 12 次提交
  7. 29 10月, 2015 2 次提交
  8. 15 10月, 2015 1 次提交
  9. 25 9月, 2015 2 次提交
    • S
      IB/mlx5: Remove pa_lkey usages · 81fb5e26
      Sagi Grimberg 提交于
      Since mlx5 driver cannot rely on registration using the
      reserved lkey (global_dma_lkey) it used to allocate a private
      physical address lkey for each allocated pd.
      Commit 96249d70 ("IB/core: Guarantee that a local_dma_lkey
      is available") just does it in the core layer so we can go ahead
      and use that.
      Signed-off-by: NSagi Grimberg <sagig@mellanox.com>
      Signed-off-by: NDoug Ledford <dledford@redhat.com>
      81fb5e26
    • S
      IB/mlx5: Remove support for IB_DEVICE_LOCAL_DMA_LKEY · c6790aa9
      Sagi Grimberg 提交于
      Commit 96249d70 ("IB/core: Guarantee that a local_dma_lkey
      is available") allows ULPs that make use of the local dma key to keep
      working as before by allocating a DMA MR with local permissions and
      converted these consumers to use the MR associated with the PD
      rather then device->local_dma_lkey.
      
      ConnectIB has some known issues with memory registration
      using the local_dma_lkey (SEND, RDMA, RECV seems to work ok).
      
      Thus don't expose support for it (remove device->local_dma_lkey
      setting), and take advantage of the above commit such that no regression
      is introduced to working systems.
      
      The local_dma_lkey support will be restored in CX4 depending on FW
      capability query.
      Signed-off-by: NSagi Grimberg <sagig@mellanox.com>
      Signed-off-by: NDoug Ledford <dledford@redhat.com>
      c6790aa9
  10. 31 8月, 2015 4 次提交
  11. 29 8月, 2015 3 次提交
  12. 13 6月, 2015 4 次提交
  13. 12 6月, 2015 1 次提交
  14. 05 6月, 2015 1 次提交
    • H
      mlx5: Enable mutual support for IB and Ethernet · 4aa17b28
      Haggai Abramonvsky 提交于
      Ethernet functionality is only available when working in ISSI > 0 mode.
      
      Previously, the IB driver wasn't ready to work on that mode, and hence
      building both the IB driver and the Ethernet functionality in the core
      driver were disallowed by Kconfigs.
      
      Now, once we have all the pre-steps in place, we can remove this limitation.
      
      The last steps in the IB driver for getting that setup to work are:
      create dummy SRQ for the driver's use (until now we could use XRC_SRQ
      as SRQ and XRC_SRQ, after moving to ISSI > 0, we separate XRC SRQs from
      basic SRQs) and adapt the create QP function to be compatible with ISSI > 0.
      Signed-off-by: NHaggai Abramovsky <hagaya@mellanox.com>
      Signed-off-by: NOr Gerlitz <ogerlitz@mellanox.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      4aa17b28