1. 06 8月, 2015 3 次提交
  2. 23 7月, 2015 1 次提交
  3. 05 6月, 2015 1 次提交
    • A
      i40e: start up in VEPA mode by default · fc60861e
      Anjali Singhai Jain 提交于
      The patch fixes a bug in the default configuration which
      prevented a software bridge loaded on the PF interface from
      working correctly because broadcast packets are incorrectly
      looped back.
      
      Fix the general case, by loading the driver in VEPA mode Until a
      VF or VMDq VSI is added. This way loopback on the Main VSI is
      turned off until needed and can resolve the issue of unnecessary
      reflection for users that do not have VF or VMDq VSIs setup.
      
      The driver must now coordinate the loopback setting for the Flow
      Director (FDIR) VSI to make sure it is in sync with the current
      VEB or VEPA mode setting.
      
      The user can still switch bridge modes from the bridge commands and
      choose to be in VEPA mode with VF VSIs. Because of hardware
      requirements, the call to switch to VEB mode when no VF/VMDqs are
      present will be rejected.
      
      NOTE: This patch uses BIT_ULL as that is preferred going forward,
      a followup patch in the lower priority queue to net-next will fix
      up the remaining 1 << usages.
      
      Change-ID: Ib121ddb18fe4b3c4f52e9deda6fcbeb9105683d1
      Signed-off-by: NAnjali Singhai Jain <anjali.singhai@intel.com>
      Signed-off-by: NJesse Brandeburg <jesse.brandeburg@intel.com>
      Tested-by: NJim Young <james.m.young@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      fc60861e
  4. 28 5月, 2015 2 次提交
  5. 03 4月, 2015 1 次提交
  6. 10 3月, 2015 1 次提交
  7. 09 3月, 2015 1 次提交
  8. 07 3月, 2015 3 次提交
  9. 05 3月, 2015 1 次提交
  10. 04 3月, 2015 1 次提交
  11. 03 3月, 2015 5 次提交
  12. 25 2月, 2015 6 次提交
  13. 24 2月, 2015 1 次提交
  14. 09 2月, 2015 2 次提交
  15. 16 1月, 2015 1 次提交
  16. 06 12月, 2014 1 次提交
  17. 18 11月, 2014 1 次提交
    • N
      i40e: Modify Tx disable wait flow in case of DCB reconfiguration · 69129dc3
      Neerav Parikh 提交于
      When DCB TC configuration changes the firmware suspends the port's Tx.
      Now, as DCB TCs may have changed the PF driver tries to reconfigure the
      TC configuration of the VSIs it manages. As part of this process it disables
      the VSI queues but the Tx queue disable will not complete as the port's
      Tx has been suspended. So, waiting for Tx queues to go to disable state
      in this flow may lead to detection of Tx queue disable timeout errors.
      
      Hence, this patch adds a new PF state so that if a port's Tx is in
      suspended state the Tx queue disable flow would just put the request for
      the queue to be disabled and return without waiting for the queue to be
      actually disabled.
      Once the VSI(s) TC reconfiguration has been done and driver has called
      firmware AQC "Resume PF Traffic" the driver checks the Tx queues requested
      to be disabled are actually disabled before re-enabling them again.
      
      Change-ID: If3e03ce4813a4e342dbd5a1eb1d2861e952b7544
      Signed-off-by: NNeerav Parikh <neerav.parikh@intel.com>
      Tested-By: NJack Morgan <jack.morgan@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      69129dc3
  18. 11 11月, 2014 1 次提交
  19. 04 9月, 2014 1 次提交
  20. 27 8月, 2014 3 次提交
  21. 03 8月, 2014 1 次提交
  22. 17 7月, 2014 2 次提交