1. 28 1月, 2023 1 次提交
  2. 24 11月, 2022 1 次提交
    • B
      ice: Accumulate HW and Netdev statistics over reset · 2fd5e433
      Benjamin Mikailenko 提交于
      Resets happen with or without user interaction. For example, incidents
      such as TX hang or a reconfiguration of parameters will result in a reset.
      During reset, hardware and software statistics were set to zero. This
      created an issue for the user where a reset happens in the background,
      statistics set to zero, and the user checks statistics expecting them to
      be populated.
      
      To ensure this doesn't happen, keep accumulating stats over reset.
      
      1. Remove function calls which reset hardware and netdev statistics.
      2. Do not rollover statistics in ice_stat_update40 during reset.
      Signed-off-by: NBenjamin Mikailenko <benjamin.mikailenko@intel.com>
      Tested-by: Gurucharan G <gurucharanx.g@intel.com> (A Contingent worker at Intel)
      Signed-off-by: NTony Nguyen <anthony.l.nguyen@intel.com>
      2fd5e433
  3. 18 11月, 2022 1 次提交
  4. 10 2月, 2022 1 次提交
    • B
      ice: Add hot path support for 802.1Q and 802.1ad VLAN offloads · 0d54d8f7
      Brett Creeley 提交于
      Currently the driver only supports 802.1Q VLAN insertion and stripping.
      However, once Double VLAN Mode (DVM) is fully supported, then both 802.1Q
      and 802.1ad VLAN insertion and stripping will be supported. Unfortunately
      the VSI context parameters only allow for one VLAN ethertype at a time
      for VLAN offloads so only one or the other VLAN ethertype offload can be
      supported at once.
      
      To support this, multiple changes are needed.
      
      Rx path changes:
      
      [1] In DVM, the Rx queue context l2tagsel field needs to be cleared so
      the outermost tag shows up in the l2tag2_2nd field of the Rx flex
      descriptor. In Single VLAN Mode (SVM), the l2tagsel field should remain
      1 to support SVM configurations.
      
      [2] Modify the ice_test_staterr() function to take a __le16 instead of
      the ice_32b_rx_flex_desc union pointer so this function can be used for
      both rx_desc->wb.status_error0 and rx_desc->wb.status_error1.
      
      [3] Add the new inline function ice_get_vlan_tag_from_rx_desc() that
      checks if there is a VLAN tag in l2tag1 or l2tag2_2nd.
      
      [4] In ice_receive_skb(), add a check to see if NETIF_F_HW_VLAN_STAG_RX
      is enabled in netdev->features. If it is, then this is the VLAN
      ethertype that needs to be added to the stripping VLAN tag. Since
      ice_fix_features() prevents CTAG_RX and STAG_RX from being enabled
      simultaneously, the VLAN ethertype will only ever be 802.1Q or 802.1ad.
      
      Tx path changes:
      
      [1] In DVM, the VLAN tag needs to be placed in the l2tag2 field of the Tx
      context descriptor. The new define ICE_TX_FLAGS_HW_OUTER_SINGLE_VLAN was
      added to the list of tx_flags to handle this case.
      
      [2] When the stack requests the VLAN tag to be offloaded on Tx, the
      driver needs to set either ICE_TX_FLAGS_HW_OUTER_SINGLE_VLAN or
      ICE_TX_FLAGS_HW_VLAN, so the tag is inserted in l2tag2 or l2tag1
      respectively. To determine which location to use, set a bit in the Tx
      ring flags field during ring allocation that can be used to determine
      which field to use in the Tx descriptor. In DVM, always use l2tag2,
      and in SVM, always use l2tag1.
      Signed-off-by: NBrett Creeley <brett.creeley@intel.com>
      Tested-by: NGurucharan G <gurucharanx.g@intel.com>
      Signed-off-by: NTony Nguyen <anthony.l.nguyen@intel.com>
      0d54d8f7
  5. 15 12月, 2021 1 次提交
  6. 21 10月, 2021 1 次提交
  7. 15 10月, 2021 2 次提交
  8. 08 10月, 2021 1 次提交
  9. 29 9月, 2021 1 次提交
  10. 26 6月, 2021 1 次提交
  11. 29 5月, 2021 1 次提交
  12. 15 4月, 2021 1 次提交
  13. 09 2月, 2021 1 次提交
  14. 29 7月, 2020 2 次提交
    • D
      ice: fix link event handling timing · 0ce6c34a
      Dave Ertman 提交于
      When the driver experiences a link event (especially link up)
      there can be multiple events generated. Some of these are
      link fault and still have a state of DOWN set.  The problem
      happens when the link comes UP during the PF driver handling
      one of the LINK DOWN events.  The status of the link is updated
      and is now seen as UP, so when the actual LINK UP event comes,
      the port information has already been updated to be seen as UP,
      even though none of the UP activities have been completed.
      
      After the link information has been updated in the link
      handler and evaluated for MEDIA PRESENT, if the state
      of the link has been changed to UP, treat the DOWN event
      as an UP event since the link is now UP.
      Signed-off-by: NDave Ertman <david.m.ertman@intel.com>
      Tested-by: NAndrew Bowers <andrewx.bowers@intel.com>
      Signed-off-by: NTony Nguyen <anthony.l.nguyen@intel.com>
      0ce6c34a
    • D
      ice: Implement LFC workaround · 7d9c9b79
      Dave Ertman 提交于
      There is a bug where the LFC settings are not being preserved
      through a link event.  The registers in question are the ones
      that are touched (and restored) when a set_local_mib AQ command
      is performed.
      
      On a link-up event, make sure that a set_local_mib is being
      performed.
      
      Move the function ice_aq_set_lldp_mib() from the DCB specific
      ice_dcb.c to ice_common.c so that the driver always has access
      to this AQ command.
      Signed-off-by: NDave Ertman <david.m.ertman@intel.com>
      Tested-by: NAndrew Bowers <andrewx.bowers@intel.com>
      Signed-off-by: NTony Nguyen <anthony.l.nguyen@intel.com>
      7d9c9b79
  15. 31 5月, 2020 1 次提交
  16. 22 5月, 2020 2 次提交
  17. 11 3月, 2020 3 次提交
  18. 20 2月, 2020 2 次提交
  19. 13 2月, 2020 3 次提交
  20. 04 1月, 2020 1 次提交
  21. 23 11月, 2019 3 次提交
  22. 09 11月, 2019 4 次提交
  23. 07 11月, 2019 1 次提交
  24. 13 9月, 2019 1 次提交
    • T
      ice: Enable DDP package download · 462acf6a
      Tony Nguyen 提交于
      Attempt to request an optional device-specific DDP package file
      (one with the PCIe Device Serial Number in its name so that different DDP
      package files can be used on different devices). If the optional package
      file exists, download it to the device. If not, download the default
      package file.
      
      Log an appropriate message based on whether or not a DDP package
      file exists and the return code from the attempt to download it to the
      device.  If the download fails and there is not already a package file on
      the device, go into "Safe Mode" where some features are not supported.
      Signed-off-by: NTony Nguyen <anthony.l.nguyen@intel.com>
      Tested-by: NAndrew Bowers <andrewx.bowers@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      462acf6a
  25. 05 9月, 2019 2 次提交
  26. 04 9月, 2019 1 次提交