1. 15 2月, 2017 3 次提交
  2. 14 2月, 2017 1 次提交
  3. 10 1月, 2017 2 次提交
    • E
      IB/mlx5: Allow future extension of libmlx5 input data · b037c29a
      Eli Cohen 提交于
      Current check requests that new fields in struct
      mlx5_ib_alloc_ucontext_req_v2 that are not known to the driver be zero.
      This was introduced so new libraries passing additional information to
      the kernel through struct mlx5_ib_alloc_ucontext_req_v2 will be notified
      by old kernels that do not support their request by failing the
      operation. This schecme is problematic since it requires libmlx5 to issue
      the requests with descending input size for struct
      mlx5_ib_alloc_ucontext_req_v2.
      
      To avoid this, we require that new features that will obey the following
      rules:
      If the feature requires one or more fields in the response and the at
      least one of the fields can be encoded such that a zero value means the
      kernel ignored the request then this field will provide the indication
      to the library. If no response is required or if zero is a valid
      response, a new field should be added that indicates to the library
      whether its request was processed.
      
      Fixes: b368d7cb ('IB/mlx5: Add hca_core_clock_offset to udata in init_ucontext')
      Signed-off-by: NEli Cohen <eli@mellanox.com>
      Reviewed-by: NMatan Barak <matanb@mellanox.com>
      Signed-off-by: NLeon Romanovsky <leon@kernel.org>
      Signed-off-by: NSaeed Mahameed <saeedm@mellanox.com>
      b037c29a
    • E
      IB/mlx5: Use blue flame register allocator in mlx5_ib · 5fe9dec0
      Eli Cohen 提交于
      Make use of the blue flame registers allocator at mlx5_ib. Since blue
      flame was not really supported we remove all the code that is related to
      blue flame and we let all consumers to use the same blue flame register.
      Once blue flame is supported we will add the code. As part of this patch
      we also move the definition of struct mlx5_bf to mlx5_ib.h as it is only
      used by mlx5_ib.
      Signed-off-by: NEli Cohen <eli@mellanox.com>
      Reviewed-by: NMatan Barak <matanb@mellanox.com>
      Signed-off-by: NLeon Romanovsky <leon@kernel.org>
      Signed-off-by: NSaeed Mahameed <saeedm@mellanox.com>
      5fe9dec0
  4. 08 1月, 2017 1 次提交
  5. 03 1月, 2017 4 次提交
  6. 14 12月, 2016 3 次提交
  7. 17 11月, 2016 2 次提交
  8. 30 10月, 2016 1 次提交
    • M
      net/mlx5: Add multi dest support · 74491de9
      Mark Bloch 提交于
      Currently when calling mlx5_add_flow_rule we accept
      only one flow destination, this commit allows to pass
      multiple destinations.
      
      This change forces us to change the return structure to a more
      flexible one. We introduce a flow handle (struct mlx5_flow_handle),
      it holds internally the number for rules created and holds an array
      where each cell points the to a flow rule.
      
      From the consumers (of mlx5_add_flow_rule) point of view this
      change is only cosmetic and requires only to change the type
      of the returned value they store.
      
      From the core point of view, we now need to use a loop when
      allocating and deleting rules (e.g given to us a flow handler).
      Signed-off-by: NMark Bloch <markb@mellanox.com>
      Signed-off-by: NSaeed Mahameed <saeedm@mellanox.com>
      Signed-off-by: NLeon Romanovsky <leon@kernel.org>
      74491de9
  9. 08 10月, 2016 6 次提交
  10. 03 9月, 2016 1 次提交
  11. 14 8月, 2016 1 次提交
  12. 23 6月, 2016 6 次提交
  13. 14 5月, 2016 4 次提交
  14. 06 4月, 2016 1 次提交
  15. 22 3月, 2016 1 次提交
    • E
      IB/mlx5: Implement callbacks for manipulating VFs · eff901d3
      Eli Cohen 提交于
      Implement the IB defined callbacks used to manipulate the policy for the
      link state, set GUIDs or get statistics information. This functionality
      is added into a new file that will be used to add any SRIOV related
      functionality to the mlx5 IB layer.
      
      The following callbacks have been added:
      
      mlx5_ib_get_vf_config
      mlx5_ib_set_vf_link_state
      mlx5_ib_get_vf_stats
      mlx5_ib_set_vf_guid
      
      In addition, publish whether this device is based on a virtual function.
      
      In mlx5 supported devices, virtual functions are implemented as vHCAs.
      vHCAs have their own QP number space so it is possible that two vHCAs
      will use a QP with the same number at the same time.
      Signed-off-by: NEli Cohen <eli@mellanox.com>
      Reviewed-by: NOr Gerlitz <ogerlitz@mellanox.com>
      Signed-off-by: NDoug Ledford <dledford@redhat.com>
      eff901d3
  16. 10 3月, 2016 1 次提交
  17. 05 3月, 2016 2 次提交