1. 23 8月, 2019 1 次提交
  2. 15 6月, 2019 1 次提交
  3. 04 5月, 2019 1 次提交
  4. 17 4月, 2019 1 次提交
  5. 15 11月, 2018 1 次提交
  6. 08 8月, 2018 1 次提交
  7. 28 4月, 2018 1 次提交
  8. 24 3月, 2018 1 次提交
  9. 27 1月, 2018 2 次提交
  10. 24 1月, 2018 1 次提交
  11. 22 11月, 2017 1 次提交
  12. 03 10月, 2017 2 次提交
  13. 20 4月, 2017 1 次提交
    • J
      i40e: reduce wait time for adminq command completion · 9e3f23f4
      Jacob Keller 提交于
      When sending an adminq command, we wait for the command to complete in
      a loop. This loop waits for an entire millisecond, when in practice the
      adminq command is processed often much faster.
      
      Change the loop to use i40e_usec_delay instead, and wait for 50 usecs
      each time instead. This appears to be about the minimum time required,
      based on some manual observation and testing.
      
      The primary benefit of this change is reducing latency of various
      operations in the PF driver, especially when related to having a large
      number of VFs enabled.
      
      For example, on Linux, when instantiating 128 VFs, the time to finish
      the operation dropped from about 9 seconds down to under 6 seconds.
      Additionally, the time it takes to finish a PF reset with 128 VFs
      dropped from 5.1 seconds down to 0.7 seconds.
      
      As the examples above show, a significant portion of the delay is wasted
      waiting for admiqn operations which have already finished.
      
      This patch shouldn't cause impact to functionality, as we still check
      and keep waiting until the command does get processed. The only expected
      change is an increase in CPU utilization as we now check for completion
      far more times. However, in practice the commands appear to generally be
      complete within the first delay window anyways.
      
      Change-ID: If8af8388e100da0a14eaf9e1af3afadf73a958cf
      Signed-off-by: NJacob Keller <jacob.e.keller@intel.com>
      Tested-by: NAndrew Bowers <andrewx.bowers@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      9e3f23f4
  14. 01 11月, 2016 1 次提交
  15. 02 5月, 2016 1 次提交
  16. 07 4月, 2016 2 次提交
  17. 18 2月, 2016 1 次提交
  18. 04 12月, 2015 1 次提交
  19. 14 10月, 2015 1 次提交
  20. 09 10月, 2015 1 次提交
  21. 08 10月, 2015 1 次提交
  22. 07 10月, 2015 1 次提交
  23. 04 10月, 2015 1 次提交
  24. 29 9月, 2015 1 次提交
  25. 18 9月, 2015 3 次提交
  26. 05 3月, 2015 1 次提交
  27. 03 3月, 2015 1 次提交
  28. 10 12月, 2014 2 次提交
  29. 06 12月, 2014 2 次提交
  30. 21 11月, 2014 1 次提交
    • M
      i40e: don't overload fields · 1001dc37
      Mitch Williams 提交于
      Overloading the msg_size field in the arq_event_info struct is just a
      bad idea. It leads to repeated bugs when the structure is used in a
      loop, since the input value (buffer size) is overwritten by the output
      value (actual message length).
      
      Fix this by splitting the field into two and renaming to indicate the
      actual function of each field.
      
      Since the arq_event struct has now changed, we need to change the drivers
      to support this. Note that we no longer need to initialize the buffer size
      each time we go through a loop as this value is no longer destroyed by
      arq processing.
      
      In the process, we also fix a bug in i40evf_verify_api_ver where the
      buffer size was not correctly reinitialized each time through the loop.
      
      Change-ID: Ic7f9633cdd6f871f93e698dfb095e29c696f5581
      Signed-off-by: NMitch Williams <mitch.a.williams@intel.com>
      Acked-by: NShannon Nelson <shannon.nelson@intel.com>
      Acked-by: NAshish Shah <ashish.n.shah@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      1001dc37
  31. 11 11月, 2014 1 次提交
  32. 27 8月, 2014 1 次提交
  33. 24 7月, 2014 1 次提交