1. 04 Oct, 2017 1 commit
  2. 03 Oct, 2017 36 commits
  3. 02 Oct, 2017 3 commits
    • David S. Miller's avatar
      Merge branch '40GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue · 4efac6ff
      David S. Miller authored
      Jeff Kirsher says:
      
      ====================
      40GbE Intel Wired LAN Driver Updates 2017-10-02
      
      This series contains updates to i40e and i40evf.
      
      Shannon Nelson fixes an issue where when a machine has more CPUs than
      queue pairs, the counting gets a "little funky" and turns off Flow
      Director.  So to correct it, limit the number of LAN queues initially
      allocated to be sure there are some left for Flow Director and other
      features.
      
      Lihong cleans up dead code by removing a condition check which cannot
      ever be true.
      
      Christophe Jaillet fixes a potential NULL pointer dereference, which
      could happen if kzalloc() fails.
      
      Filip corrects the reporting of supported link modes, which was incorrect
      for some NICs.  Added support for 'ethtool -m' command, which displays
      information about QSFP+ modules.
      
      Mariusz adds functions to read/write the LED registers to control the
      LEDS, instead of accessing the registers directly whenever the LEDs
      need to be controlled.
      
      Jake fixes a regression where we introduced a scheduling while atomic,
      so introduce a separate helper function which will manage its own need
      for the mac_filter_hash_lock.  Also cleaned up the "PF" parameter in
      i40e_vc_disable_vf() since it is never used and is not needed.  Fixed
      a rare case where it is possible that a reset does not occur when
      i40e_vc_disable_vf() is called, so modify i40e_reset_vf() to return a
      bool to indicate whether it reset or not so that i40e_vc_disable_vf()
      can wait until a reset actually occurs.
      
      Alan adds the ability for the VF to request more or less underlying
      allocated queues from the PF.  Fixes the incorrect method for clearing
      the vf_states variable with a NULL assignment, when we should be
      using atomic bitops since we don't actually want to clear all the
      flags.  Fixed a resource leak, where the PF driver fails to inform
      clients of a VF reset because we were incorrectly checking the
      I40E_VF_STATE_PRE_ENABLE bit.
      
      Mitch converts i40evf_map_rings_to_vectors() to a void function since
      it cannot fail and allows us to clean up the checks for the function
      return value.
      
      Scott enables the driver(s) to pass traffic with VLAN tags using the
      802.1ad Ethernet protocol.
      ====================
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      4efac6ff
    • Scott Peterson's avatar
      i40e: Stop dropping 802.1ad tags - eth proto 0x88a8 · ab243ec9
      Scott Peterson authored
      Enable i40e to pass traffic with VLAN tags using the 802.1ad ethernet
      protocol ID (0x88a8).
      
      This requires NIC firmware providing version 1.7 of the API. With
      older NIC firmware 802.1ad tagged packets will continue to be dropped.
      
      No VLAN offloads nor RSS are supported for 802.1ad VLANs.
      Signed-off-by: default avatarScott Peterson <scott.d.peterson@intel.com>
      Tested-by: default avatarAndrew Bowers <andrewx.bowers@intel.com>
      Signed-off-by: default avatarJeff Kirsher <jeffrey.t.kirsher@intel.com>
      ab243ec9
    • Alan Brady's avatar
      i40e: fix client notify of VF reset · c53d11f6
      Alan Brady authored
      Currently there is a bug in which the PF driver fails to inform clients
      of a VF reset which then causes clients to leak resources.  The bug
      exists because we were incorrectly checking the I40E_VF_STATE_PRE_ENABLE
      bit.
      
      When a VF is first init we go through a reset to initialize variables
      and allocate resources but we don't want to inform clients of this first
      reset since the client isn't fully enabled yet so we set a state bit
      signifying we're in a "pre-enabled" client state.  During the first
      reset we should be clearing the bit, allowing all following resets to
      notify the client of the reset when the bit is not set.  This patch
      fixes the issue by negating the 'test_and_clear_bit' check to accurately
      reflect the behavior we want.
      Signed-off-by: default avatarAlan Brady <alan.brady@intel.com>
      Tested-by: default avatarAndrew Bowers <andrewx.bowers@intel.com>
      Signed-off-by: default avatarJeff Kirsher <jeffrey.t.kirsher@intel.com>
      c53d11f6