1. 17 2月, 2016 1 次提交
  2. 04 2月, 2016 4 次提交
  3. 03 12月, 2015 1 次提交
    • J
      i40e: use priv flags to control packet split · 827de392
      Jesse Brandeburg 提交于
      Ethtool priv flags implementation to enable or disable packet split, which
      is a hardware feature that inspects headers and will put headers in a
      separate DMA buffer from the payload data.  The driver was automatically
      choosing to enable packet split in some cases and this gives the user the
      ability to turn it off/on explicitly.
      
      to query state:
      ethtool --show-priv-flags ethx
      
      to enable:
      ethtool --set-priv-flags ethx packet-split on
      to disable:
      ethtool --set-priv-flags ethx packet-split off
      
      Why would anyone want this?
      	Because some environments benefit from header/data split in the receive
      	buffer, and the driver defaults to one or the other depending on
      	environment/kernel parameters.
      
      Why didn't you implement a generic ethtool control for this feature?
      	Because Intel hardware is the only hardware that supports header/data
      	split.
      
      Change-ID: I803121e1eecc9ccb2884031fd85dd1110b3af66d
      Signed-off-by: NJesse Brandeburg <jesse.brandeburg@intel.com>
      Tested-by: NAndrew Bowers <andrewx.bowers@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      827de392
  4. 02 12月, 2015 1 次提交
  5. 26 11月, 2015 4 次提交
  6. 23 10月, 2015 1 次提交
  7. 20 10月, 2015 2 次提交
  8. 16 10月, 2015 6 次提交
  9. 15 10月, 2015 3 次提交
  10. 14 10月, 2015 2 次提交
    • C
      i40e/i40evf: Refactor PHY structure and add phy_capabilities enum · fc72dbce
      Catherine Sullivan 提交于
      Remove unused members in the PHY structure and add a new member to store
      all the capabilities the PHY has as reported by the FW. This information
      will help us determine what speeds the device is capable of when link is
      down.
      
      Also add an enum to decode the PHY types the NVM is capable of.
      Use the phy_types variable to determine what phy types are possible
      when link is down instead of device id as it will be more accurate.
      
      When on a backplane device, we do not support changing any settings,
      however we should display all the phy_types we are capable of so if we
      see a backplane dev ID set supported and advertised purely based on
      the phy_types variable.
      
      Change-ID: Ia75d560f1fcd30c54cbfb7458690c5867559a930
      Signed-off-by: NCatherine Sullivan <catherine.sullivan@intel.com>
      Tested-by: NAndrew Bowers <andrewx.bowers@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      fc72dbce
    • C
      i40e/i40evf: Add module_types and update_link_info · 0a862b43
      Catherine Sullivan 提交于
      Add a module_types variable to the link_info struct to save the module
      information from get_phy_capabilities. This information can be used to
      determine which speeds the module supports.
      
      Also add a new function update_link_info which updates the module_types
      parameter and then calls get_link_info. This function should be called
      in place of get_link_info so that the module_types variable stays
      up-to-date with the rest of the link information.
      
      The EAS table does not reflect the values that are actually returned,
      so instead, basing these values on the Ethernet compliance codes
      specified in table 33 of SFF-8436 as these have been accurate.
      
      Use the new variable in ethtool to differentiate between a 10G/1G dual
      speed fiber module and a 10G only module.
      
      Change-ID: Ib7585cce321319c10ce15180054c41a6cbd41389
      Signed-off-by: NCatherine Sullivan <catherine.sullivan@intel.com>
      Tested-by: NAndrew Bowers <andrewx.bowers@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      0a862b43
  11. 09 10月, 2015 4 次提交
  12. 08 10月, 2015 4 次提交
  13. 30 9月, 2015 2 次提交
  14. 27 8月, 2015 5 次提交