1. 25 4月, 2016 1 次提交
  2. 22 3月, 2016 2 次提交
  3. 10 3月, 2016 1 次提交
  4. 05 3月, 2016 3 次提交
  5. 02 3月, 2016 4 次提交
  6. 01 3月, 2016 1 次提交
  7. 25 2月, 2016 1 次提交
  8. 03 2月, 2016 2 次提交
  9. 22 1月, 2016 3 次提交
  10. 20 1月, 2016 3 次提交
  11. 12 1月, 2016 1 次提交
  12. 24 12月, 2015 12 次提交
  13. 29 10月, 2015 2 次提交
  14. 15 10月, 2015 1 次提交
  15. 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
  16. 31 8月, 2015 1 次提交