1. 03 12月, 2015 3 次提交
  2. 02 12月, 2015 3 次提交
  3. 26 11月, 2015 3 次提交
  4. 23 10月, 2015 1 次提交
  5. 20 10月, 2015 2 次提交
  6. 16 10月, 2015 5 次提交
  7. 15 10月, 2015 2 次提交
  8. 14 10月, 2015 1 次提交
  9. 09 10月, 2015 4 次提交
  10. 08 10月, 2015 3 次提交
  11. 30 9月, 2015 2 次提交
  12. 29 9月, 2015 2 次提交
  13. 02 9月, 2015 1 次提交
    • A
      i40e: Set defport behavior for the Main VSI when in promiscuous mode · 92faef85
      Anjali Singhai Jain 提交于
      This fixes bugs where the port is not receiving multicast or VLAN tagged
      packets when in promiscuous mode. This can occur when a SW bridge is
      created on top of the device.
      
      This also fixes issues where the promiscuous behavior setting was not
      being preserved across a reset caused by features being enabled or
      disabled.
      
      We are using defport instead of doing a true promiscuous mode because we do
      not need to receive the SRIOV or VMDq VSI directed traffic which would suck
      up bandwidth and is really not intended for the SW bridge.
      
      In addition, with defport we get VLAN promiscuous behavior which is not
      possible from the VSI level promiscuous setting.
      
      Change-ID: Ie21985eac32d5af1c02e9d71c6430a90d5bab40f
      Signed-off-by: NAnjali Singhai Jain <anjali.singhai@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      92faef85
  14. 27 8月, 2015 1 次提交
  15. 06 8月, 2015 3 次提交
  16. 23 7月, 2015 1 次提交
  17. 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
  18. 28 5月, 2015 2 次提交