1. 14 6月, 2019 1 次提交
  2. 01 6月, 2019 4 次提交
  3. 14 5月, 2019 1 次提交
  4. 02 5月, 2019 1 次提交
  5. 30 4月, 2019 5 次提交
  6. 25 4月, 2019 2 次提交
  7. 03 4月, 2019 1 次提交
  8. 23 3月, 2019 1 次提交
  9. 23 2月, 2019 1 次提交
    • E
      net/mlx5: Introduce tunnel entropy control in PCMR register · 0dcaafc0
      Eli Britstein 提交于
      When using the device packet encapsulation offload, the device
      calculates an entropy value, representing the inner packet headers. The
      entropy field is placed inside the outer packet headers. For UDP-type
      encapsulations, the entropy is placed in the source port field of the
      UDP header. For GRE-type encapsulations, the entropy is placed in the 8
      LSB of the key field in the GRE header. If the device does not recognize
      the encapsulation type, the entropy is not placed in the packet.
      
      Entropy setting can be controlled using PCMR register. if encapsulation
      offload is not used force_entropy_cap should be set to 0x0. Entropy
      setting is enabled/disabled using entropy_calc, and could be
      additionally enabled/disabled for GRE encapsulation by entropy_gre_calc.
      
      As a pre-step to automatically control the tunnel entropy, introduce
      the entropy fields in the PCMR register with no functional change.
      Signed-off-by: NEli Britstein <elibr@mellanox.com>
      Reviewed-by: NOz Shlomo <ozsh@mellanox.com>
      Reviewed-by: NRoi Dayan <roid@mellanox.com>
      Signed-off-by: NSaeed Mahameed <saeedm@mellanox.com>
      0dcaafc0
  10. 16 2月, 2019 1 次提交
  11. 15 2月, 2019 4 次提交
    • A
      net/mlx5: Add new fields to Port Type and Speed register · a0a89989
      Aya Levin 提交于
      Register Port Type and Speed (PTYS) introduces three new fields
      extending the speed/protocols the can be reported and configured.
      Signed-off-by: NAya Levin <ayal@mellanox.com>
      Reviewed-by: NEran Ben Elisha <eranbe@mellanox.com>
      Signed-off-by: NSaeed Mahameed <saeedm@mellanox.com>
      a0a89989
    • B
      net/mlx5: Add query host params command · c3a4e9f1
      Bodong Wang 提交于
      The QUERY_HOST_PARAMS command is used by an Embedded CPU Physical
      Function (ECPF) driver to identify and retrieve information about the
      PF on the host side. E.g, number of virtual functions and PCI BDF.
      
      The number of VFs can be changed on the fly, a function is added to
      query current number of VFs and will be used in downstream patches.
      Signed-off-by: NBodong Wang <bodong@mellanox.com>
      Signed-off-by: NEli Cohen <eli@mellanox.com>
      Reviewed-by: NOr Gerlitz <ogerlitz@mellanox.com>
      Signed-off-by: NSaeed Mahameed <saeedm@mellanox.com>
      c3a4e9f1
    • B
      net/mlx5: Update enable HCA dependency · 22e939a9
      Bodong Wang 提交于
      With the introduction of ECPF, we require that the ECPF driver will
      aways call enable/disable HCA for that PF in the same way a PF does
      this for its VFs. The PF is still responsible for calling enable and
      disable HCA for its VFs.
      
      To distinguish between the ECPF executing enable/disable HCA for
      itself or for the PF, it sets the embedded CPU function bit in the
      input params struct of these commands. When the bit is cleared and
      function ID is zero, it refers to the peer PF.
      Signed-off-by: NBodong Wang <bodong@mellanox.com>
      Signed-off-by: NEli Cohen <eli@mellanox.com>
      Signed-off-by: NSaeed Mahameed <saeedm@mellanox.com>
      22e939a9
    • B
      net/mlx5: Introduce Mellanox SmartNIC and modify page management logic · 591905ba
      Bodong Wang 提交于
      Mellanox's SmartNIC combines embedded CPU(e.g, ARM) processing power
      with advanced network offloads to accelerate a multitude of security,
      networking and storage applications.
      
      With the introduction of the SmartNIC, there is a new PCI function
      called Embedded CPU Physical Function(ECPF). And it's possible for a
      PF to get its ICM pages from the ECPF PCI function. Driver shall
      identify if it is running on such a function by reading a bit in
      the initialization segment.
      
      When firmware asks for pages, it would issue a page request event
      specifying how many pages it requests and for which function. That
      driver responds with a manage_pages command providing the requested
      pages along with an indication for which function it is providing these
      pages.
      
      The encoding before this patch was as follows:
          function_id == 0: pages are requested for the function receiving
                            the EQE.
          function_id != 0: pages are requested for VF identified by the
                            function_id value
      
      A new one bit field in the EQE identifies that pages are requested for
      the ECPF.
      
      The notion of page_supplier can be introduced here and to support that,
      manage pages and query pages were modified so firmware can distinguish
      the following cases:
      
      1. Function provides pages for itself
      2. PF provides pages for its VF
      3. ECPF provides pages to itself
      4. ECPF provides pages for another function
      
      This distinction is possible through the introduction of the bit
      "embedded_cpu_function" in query_pages, manage_pages and page request
      EQE.
      Signed-off-by: NBodong Wang <bodong@mellanox.com>
      Signed-off-by: NEli Cohen <eli@mellanox.com>
      Signed-off-by: NSaeed Mahameed <saeedm@mellanox.com>
      591905ba
  12. 03 2月, 2019 2 次提交
  13. 21 12月, 2018 1 次提交
  14. 20 12月, 2018 1 次提交
  15. 19 12月, 2018 1 次提交
  16. 15 12月, 2018 2 次提交
  17. 13 12月, 2018 1 次提交
  18. 12 12月, 2018 1 次提交
  19. 11 12月, 2018 3 次提交
  20. 07 12月, 2018 1 次提交
  21. 05 12月, 2018 1 次提交
  22. 04 12月, 2018 1 次提交
  23. 09 11月, 2018 1 次提交
  24. 07 11月, 2018 1 次提交
  25. 19 10月, 2018 1 次提交