1. 15 12月, 2018 1 次提交
  2. 11 12月, 2018 1 次提交
  3. 10 12月, 2018 1 次提交
  4. 04 12月, 2018 8 次提交
  5. 30 11月, 2018 3 次提交
    • S
      IB/mlx5: Handle raw delay drop general event · 09e574fa
      Saeed Mahameed 提交于
      Handle FW general event rq delay drop as it was received from FW via mlx5
      notifiers API, instead of handling the processed software version of that
      event. After this patch we can safely remove all software processed FW
      events types and definitions.
      Signed-off-by: NSaeed Mahameed <saeedm@mellanox.com>
      09e574fa
    • S
      IB/mlx5: Handle raw port change event rather than the software version · 134e9349
      Saeed Mahameed 提交于
      Use the FW version of the port change event as forwarded via new mlx5
      notifiers API.
      
      After this patch, processed software version of the port change event
      will become deprecated and will be totally removed in downstream
      patches.
      Signed-off-by: NSaeed Mahameed <saeedm@mellanox.com>
      134e9349
    • S
      IB/mlx5: Use the new mlx5 core notifier API · df097a27
      Saeed Mahameed 提交于
      Remove the deprecated mlx5_interface->event mlx5_ib callback and use new
      mlx5 notifier API to subscribe for mlx5 events.
      
      For native mlx5_ib devices profiles pf_profile/nic_rep_profile register
      the notifier callback mlx5_ib_handle_event which treats the notifier
      context as mlx5_ib_dev.
      
      For vport repesentors, don't register any notifier, same as before, they
      didn't receive any mlx5 events.
      
      For slave port (mlx5_ib_multiport_info) register a different notifier
      callback mlx5_ib_event_slave_port, which knows that the event is coming
      for mlx5_ib_multiport_info and prepares the event job accordingly.
      Before this on the event handler work we had to ask mlx5_core if this is
      a slave port mlx5_core_is_mp_slave(work->dev), now it is not needed
      anymore.
      mlx5_ib_multiport_info notifier registration is done on
      mlx5_ib_bind_slave_port and de-registration is done on
      mlx5_ib_unbind_slave_port.
      Signed-off-by: NSaeed Mahameed <saeedm@mellanox.com>
      df097a27
  6. 21 11月, 2018 2 次提交
  7. 13 11月, 2018 2 次提交
  8. 27 10月, 2018 1 次提交
  9. 19 10月, 2018 1 次提交
    • T
      net/mlx5: Refactor fragmented buffer struct fields and init flow · 4972e6fa
      Tariq Toukan 提交于
      Take struct mlx5_frag_buf out of mlx5_frag_buf_ctrl, as it is not
      needed to manage and control the datapath of the fragmented buffers API.
      
      struct mlx5_frag_buf contains control info to manage the allocation
      and de-allocation of the fragmented buffer.
      Its fields are not relevant for datapath, so here I take them out of the
      struct mlx5_frag_buf_ctrl, except for the fragments array itself.
      
      In addition, modified mlx5_fill_fbc to initialise the frags pointers
      as well. This implies that the buffer must be allocated before the
      function is called.
      
      A set of type-specific *_get_byte_size() functions are replaced by
      a generic one.
      Signed-off-by: NTariq Toukan <tariqt@mellanox.com>
      Signed-off-by: NSaeed Mahameed <saeedm@mellanox.com>
      4972e6fa
  10. 18 10月, 2018 2 次提交
  11. 17 10月, 2018 8 次提交
  12. 16 10月, 2018 10 次提交