1. 11 5月, 2016 2 次提交
    • S
      iwlwifi: mvm: add reorder buffer per queue · b915c101
      Sara Sharon 提交于
      Next hardware will direct packets to core based on the TCP/UDP
      streams.
      This logic can create holes in reorder buffer since packets that
      belong to other stream were directed to a different core.
      However, those are valid holes and the packets can be indicated
      in L3 order.
      
      The hardware will utilize a mechanism of informing the driver of
      the normalized ssn and the driver shall release all packets that
      SN is lower than the nssn.
      This enables managing the reorder across the queues without sharing
      any data between them.
      
      The reorder buffer is allocated and released directly in the RX path
      in order to avoid various races between control path and rx path.
      The code utilizes the internal messaging to notify rx queues of when
      to delete the reorder buffer.
      Signed-off-by: NSara Sharon <sara.sharon@intel.com>
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      b915c101
    • S
      iwlwifi: mvm: add infrastructure for tracking BA session in driver · 10b2b201
      Sara Sharon 提交于
      According to the spec when a BA session is started there
      is a timeout set for the session in the ADDBA request.
      If there is not activity on the TA/TID then the session
      expires and a DELBA is sent.
      In order to check for the timeout, data must be shared
      among the rx queues.
      Add a timer that runs as long as BA session is active
      for the station and stops aggregation session if needed.
      This patch also lays the infrastructure for the reordering
      buffer which will be enabled in the next patches.
      Signed-off-by: NSara Sharon <sara.sharon@intel.com>
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      10b2b201
  2. 30 3月, 2016 1 次提交
    • L
      iwlwifi: mvm: support bss dynamic alloc/dealloc of queues · 24afba76
      Liad Kaufman 提交于
      "DQA" is shorthand for "dynamic queue allocation". This
      enables on-demand allocation of queues per RA/TID rather than
      statically allocating per vif, thus allowing a potential
      benefit of various factors.
      
      Please refer to the DOC section this patch adds to sta.h to
      see a more in-depth explanation of this feature.
      
      There are many things to take into consideration when working
      in DQA mode, and this patch is only one in a series. Note that
      default operation mode is non-DQA mode, unless the FW
      indicates that it supports DQA mode.
      
      This patch enables support of DQA for a station connected to
      an AP, and works in a non-aggregated mode.
      
      When a frame for an unused RA/TID arrives at the driver, it
      isn't TXed immediately, but deferred first until a suitable
      queue is first allocated for it, and then TXed by a worker
      that both allocates the queues and TXes deferred traffic.
      
      When a STA is removed, its queues goes back into the queue
      pools for reuse as needed.
      Signed-off-by: NLiad Kaufman <liad.kaufman@intel.com>
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      24afba76
  3. 28 2月, 2016 4 次提交
  4. 01 2月, 2016 1 次提交
  5. 08 1月, 2016 1 次提交
    • J
      iwlwifi: mvm: check PN for CCMP/GCMP in the driver · f5e28eac
      Johannes Berg 提交于
      As we're working on multi-queue RX, we want to parallelise checking
      the PN in order to avoid having to serialise the RX processing.
      
      It may seem that doing parallel PN checking is insecure, but it turns
      out to be OK because queue assignment is done based on the data in the
      frame (IP/TCP) and thus cannot be manipulated by an attacker, since
      the data is encrypted and must first have been decrypted successfully.
      
      There are some corner cases, in particular when the peer starts using
      fragmentation which redirects the packet to the default queue. However
      this redirection is remembered (for the STA, per TID) and thus cannot
      be exploited by an attacker either.
      
      Leave checking on the default queue (queue 0) to mac80211, since we
      get fragmented packets there and those are subject to stricter checks
      during reassembly.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      Signed-off-by: NSara Sharon <sara.sharon@intel.com>
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      f5e28eac
  6. 21 12月, 2015 1 次提交
  7. 20 12月, 2015 1 次提交
  8. 13 12月, 2015 1 次提交
  9. 18 11月, 2015 1 次提交
  10. 16 11月, 2015 1 次提交
    • L
      iwlwifi: mvm: don't overwrite the key indices in D3 entry · d6ee54a9
      Luca Coelho 提交于
      When entering D3, we need to use hardcoded key indices because the
      firmware requires that.  To do so, we are overwriting the HW key index
      in the keyconf structure, which makes it impossible to reuse the
      indices that were used before entering D3.  Additionally, we overwrite
      all the non-PTK keys with index 1, because the firmware only allows
      one non-PTK key to be set.  This is bad, because when we resume, we
      may try to set more than one key with index 1, which will obviously
      fail.
      
      To fix this, allow the callers to set a pre-defined index to use in
      iwl_mvm_set_sta_key() instead of relying on the hw_key_idx value from
      the keyconf struct (which requires overwriting it).  In normal cases,
      the caller can pass STA_KEY_IDX_INVALID, which will cause a new key
      offset to be chosen.  During HW_RESTART, we pass the offset that is in
      use.  And during D3 entry, we pass the hardcoded indices we need to
      use.
      
      Additionally, don't clear the fw_key_table in D3 entry, so that the
      flags are still set with the pre-D3 values when exiting D3.
      
      fixes=I3165c22362483f0152d9ec1d2a987fb5529727c1
      
      Fixes: b546dcd6 ("iwlwifi: mvm: don't reset key index on HW restart")
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      d6ee54a9
  11. 04 8月, 2015 1 次提交
  12. 02 4月, 2015 1 次提交
  13. 24 11月, 2014 3 次提交
  14. 21 9月, 2014 1 次提交
  15. 04 9月, 2014 3 次提交
  16. 08 7月, 2014 1 次提交
  17. 25 6月, 2014 1 次提交
  18. 22 5月, 2014 1 次提交
  19. 10 4月, 2014 1 次提交
  20. 07 2月, 2014 1 次提交
  21. 04 2月, 2014 2 次提交
  22. 01 1月, 2014 1 次提交
  23. 10 12月, 2013 1 次提交
  24. 03 10月, 2013 1 次提交
  25. 12 6月, 2013 1 次提交
  26. 29 5月, 2013 1 次提交
  27. 17 5月, 2013 1 次提交
    • E
      iwlwifi: mvm: fix aggregation drain flow · e3d4bc8c
      Emmanuel Grumbach 提交于
      Move the counter for non-AMPDU frames to mvm. It is needed
      for the drain flow which happens once the ieee80211_sta has
      been freed, so keeping it in iwl_mvm_sta which is embed into
      ieee80211_sta is not a good idea.
      
      Also, since its purpose it to remove the STA in the fw only
      after all the frames for this station have exited the shared
      Tx queues, we need to decrement it in the reclaim flow. This
      flow can happen after ieee80211_sta has been removed, which
      means that we have no iwl_mvm_sta there. So we can't know
      what is the vif type. Hence, we know audit these frames for
      all the vif types.
      In order to avoid spawning sta_drained_wk all the time, we
      now check that we are in a flow in which draining might
      happen - only when mvmsta is NULL. This is better than
      previous code that would spawn sta_drained_wk all the time
      in AP mode.
      
      Cc: stable@vger.kernel.org [3.9]
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      Reviewed-by: NIlan Peer <ilan.peer@intel.com>
      Reviewed-by: NJohannes Berg <johannes.berg@intel.com>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      e3d4bc8c
  28. 04 4月, 2013 1 次提交
  29. 06 3月, 2013 2 次提交
  30. 19 2月, 2013 1 次提交