1. 04 8月, 2019 1 次提交
  2. 26 7月, 2019 1 次提交
  3. 09 7月, 2019 1 次提交
    • M
      IB/mlx5: Implement VHCA tunnel mechanism in DEVX · b6142608
      Max Gurtovoy 提交于
      This mechanism will allow function-A to perform operations "on behalf" of
      function-B via tunnel object. Function-A will have privileges for creating
      and using this tunnel object.
      
      For example, in the device emulation feature presented in Bluefield-1 SoC,
      using device emulation capability, one can present NVMe function to the
      host OS.
      
      Since the NVMe function doesn't have a normal command interface to the HCA
      HW, here is a need to create a channel that will be able to issue commands
      "on behalf" of this function.
      
      This channel is the VHCA_TUNNEL general object. The emulation software
      will create this tunnel for every managed function and issue commands via
      devx general cmd interface using the appropriate tunnel ID. When devX
      context will receive a command with non-zero vhca_tunnel_id, it will pass
      the command as-is down to the HCA.
      
      All the validation, security and resource tracking of the commands and the
      created tunneled objects is in the responsibility of the HCA FW. When a
      VHCA_TUNNEL object destroyed, the device will issue an internal
      FLR (function level reset) to the emulated function associated with this
      tunnel. This will destroy all the created resources using the tunnel
      mechanism.
      Signed-off-by: NMax Gurtovoy <maxg@mellanox.com>
      Reviewed-by: NYishai Hadas <yishaih@mellanox.com>
      Signed-off-by: NLeon Romanovsky <leonro@mellanox.com>
      Signed-off-by: NJason Gunthorpe <jgg@mellanox.com>
      b6142608
  4. 04 7月, 2019 6 次提交
  5. 25 6月, 2019 1 次提交
  6. 14 5月, 2019 1 次提交
  7. 06 5月, 2019 1 次提交
  8. 23 4月, 2019 2 次提交
  9. 11 4月, 2019 1 次提交
  10. 09 4月, 2019 1 次提交
  11. 02 4月, 2019 1 次提交
  12. 28 3月, 2019 1 次提交
  13. 18 3月, 2019 1 次提交
  14. 16 2月, 2019 1 次提交
  15. 12 2月, 2019 1 次提交
  16. 31 1月, 2019 1 次提交
  17. 30 1月, 2019 4 次提交
  18. 22 1月, 2019 2 次提交
  19. 11 1月, 2019 1 次提交
  20. 21 12月, 2018 1 次提交
  21. 07 12月, 2018 1 次提交
  22. 05 12月, 2018 3 次提交
  23. 30 11月, 2018 1 次提交
  24. 27 11月, 2018 2 次提交
  25. 23 11月, 2018 2 次提交
  26. 16 10月, 2018 1 次提交