1. 31 Aug, 2018 1 commit
    • David S. Miller's avatar
      Merge branch '40GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue · ee713b6d
      David S. Miller authored
      Jeff Kirsher says:
      
      ====================
      40GbE Intel Wired LAN Driver Updates 2018-08-30
      
      This series contains updates to i40e, i40evf and virtchnl.
      
      Jake implements helper functions to use an array to handle the queue
      stats which reduces the boiler plate code as well as keep the complexity
      localized to a few functions.
      
      Paweł adds the ability to change a VF's MAC address from the host side
      without having to reload the VF driver on the guest side.
      
      Paul adds a check to ensure that the number of queues that the PF sends
      to the VF is equal to or less than the maximum number of queues the VF
      can support.
      
      Mitch fixes an issue caught by GCC 8, where we need to not include the
      terminating null in the length of the string for strncpy().
      
      Lihong fixes a VF issue to ensure that it does not enter into
      promiscuous mode when macvlan is added to the VF.  Fixed a potential
      crash after a VF is removed, since the workqueue sync for the adminq
      task was not being cancelled.
      
      Harshitha fixes the type for field_flags in the virtchnl_filter struct.
      
      Martyna removes an unnecessary check in a conditional if statement.
      
      Björn fixes an issue reported by Jesper Dangaard Brouer, where the
      driver was reporting incorrect statistics when XDP was enabled.
      
      Jan fixes the potential reporting of incorrect speed settings.
      
      Patryk fixed an issue where the flag
      I40EVF_FLAG_AQ_ENABLE_VLAN_STRIPPING was getting set when any offload is
      set via ethtool.  Resolved by only setting this flag when VLAN offload
      is enabled.  Also ensure we hold the rtnl lock when we are clearing the
      interrupt scheme.  Added a check when deleting the MAC address from the
      VF to ensure that the MAC address was not set by the PF and if it was,
      do not delete it.
      
      v2: updated patch 2 in the series based on community feedback from David
          Miller to inline a function
      ====================
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      ee713b6d
  2. 30 Aug, 2018 35 commits
  3. 29 Aug, 2018 2 commits
    • Balaji Pothunoori's avatar
      cfg80211: clarify frames covered by average ACK signal report · 9c06602b
      Balaji Pothunoori authored
      Modify the API to include all ACK frames in average ACK
      signal strength reporting, not just ACKs for data frames.
      Make exposing the data conditional on implementing the
      extended feature flag.
      
      This is how it was really implemented in mac80211, update
      the code there to use the new defines and clean up some of
      the setting code.
      
      Keep nl80211.h source compatibility by keeping the old names.
      Signed-off-by: default avatarBalaji Pothunoori <bpothuno@codeaurora.org>
      [rewrite commit log, change compatibility to be old=new
       instead of the other way around, update kernel-doc,
       roll in mac80211 changes, make mac80211 depend on valid
       bit instead of HW flag]
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      9c06602b
    • Sathishkumar Muruganandam's avatar
      mac80211: add missing WFA Multi-AP backhaul STA Rx requirement · 1ecef20c
      Sathishkumar Muruganandam authored
      The current mac80211 WDS (4-address mode) can be used to cover most of the
      Multi-AP requirements for Data frames per the WFA Multi-AP Specification v1.0.
      When configuring AP/STA interfaces in 4-address mode, they are able to function
      as fronthaul AP/backhaul STA of Multi-AP device complying below
      Tx, Rx requirements except one missing STA Rx requirement added by this patch.
      
      Multi-AP specification section 14.1 describes the following requirements:
      
      Transmitter requirements
      ------------------------
      1. Fronthaul AP
              i) When DA!=RA of backhaul STA, must use 4-address format
              ii) When DA==RA of backhaul STA, shall use either 3-address
                  or 4-address format with RA updated with STA MAC
      
                  (mac80211 support 4-address format via AP/VLAN interface)
      
      2. Backhaul STA
              i) When SA!=TA of backhaul STA, must use 4-address format
              ii) When SA==TA of backhaul STA, shall use either 3-address
                  or 4-address format with RA updated with AP MAC
      
                  (mac80211 support 4-address format via use_4addr)
      
      Receiver requirements
      ---------------------
      1. Fronthaul AP
              i) When SA!=TA of backhaul STA, must support receiving 4-address
                 format frames
              ii) When SA==TA of backhaul STA, must support receiving both
                  3-address and 4-address format frames
      
                  (mac80211 support both 3-addr & 4-addr via AP/VLAN interface)
      
      2. Backhaul STA
              i) When DA!=RA of backhaul STA, must support receiving 4-address
                 format frames
              ii) When DA==RA of backhaul STA,  must support receiving both
                  3-address and 4-address format frames
      
                  (mac80211 support only receiving 4-address format via
                   use_4addr)
      
      This patch addresses the above Rx requirement (ii) for backhaul STA to receive
      unicast (DA==RA) 3-address frames in addition to 4-address frames.
      
      The current design doesn't accept 3-address frames when configured in 4-address
      mode (use_4addr). Hence add a check to allow 3-address frames when DA==RA of
      backhaul STA (adhering to Table 9-26 of IEEE Std 802.11-2016).
      
      This case was tested with a bridged station interface when associated with
      a non-mac80211 based vendor AP implementation using 3-address frames for WDS.
      
      STA was able to support the Multi-AP Rx requirement when DA==RA. No issues,
      no loops seen when tested with mac80211 based AP as well.
      
      Verified and confirmed all other Tx and Rx requirements of AP and STA for
      Multi-AP respectively. They all work using the current mac80211-WDS design.
      Signed-off-by: default avatarSathishkumar Muruganandam <murugana@codeaurora.org>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      1ecef20c
  4. 28 Aug, 2018 2 commits
    • David S. Miller's avatar
      Merge branch 'nfp-add-NFP5000-support' · 817e60a7
      David S. Miller authored
      Jakub Kicinski says:
      
      ====================
      nfp: add NFP5000 support
      
      This series broadly speaking adds support for NFP5000 and
      related products.
      
      First we add support for loading FW from flash.  We need to allow
      for the management processor to provide extended log messages when
      FW is loaded.  This is needed when FW selection policy is to compare
      the FW on the disk and in the flash, and load the newer.  User should
      be told what FW was selected.
      
      We use this opportunity to add extended errors for normal FW loading
      as well.
      
      Next we add support for requesting HW information from the management
      processor.  Up until now the driver read the HWinfo as it appears in
      card memory, but there can be cases when management processor has
      additional information or generates the entries dynamically so
      occasionally we will have to consult it.  We use this to look up MAC
      addresses for PCIe netdevs.
      
      Next the actual patch with NFP5000 support and a small dose of
      refactoring of PCIe init.
      
      The remaining patches add support for reading RTsymbol types we
      didn't need before.  Ones explicitly placed in external memory unit's
      cache and absolute ones.
      
      This part begins with a patch moving the logic which figures out
      the correct bit offsets to device probe, to avoid redoing the
      calculation for each access.  Second patch adds error messages
      for easier troubleshooting.  Next patch adds helpers which will
      take care of address conversions to reach into EMU cache.
      Subsequently users are migrated from the raw CPP API to the new RTsym
      helpers.  Finally we add support for reading absolute symbols.
      ====================
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      817e60a7
    • Jakub Kicinski's avatar
      nfp: make RTsym users handle absolute symbols correctly · 4152e58c
      Jakub Kicinski authored
      Make the RTsym users access the size via the helper, which
      takes care of special handling of absolute symbols.
      Signed-off-by: default avatarJakub Kicinski <jakub.kicinski@netronome.com>
      Reviewed-by: default avatarFrancois H. Theron <francois.theron@netronome.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      4152e58c