diff options
author | Sara Sharon <sara.sharon@intel.com> | 2018-08-21 15:23:39 +0300 |
---|---|---|
committer | Luca Coelho <luciano.coelho@intel.com> | 2019-01-25 21:57:19 +0300 |
commit | cfbc6c4c5b91c7725ef14465b98ac347d31f2334 (patch) | |
tree | ec174a10264bd09381be46580078739dd2d83ef4 /drivers/net/wireless/intel/iwlwifi/mvm/rs-fw.c | |
parent | c281f13792f64372f49b63eab4c1ce88282448d2 (diff) | |
download | linux-cfbc6c4c5b91c7725ef14465b98ac347d31f2334.tar.xz |
iwlwifi: mvm: support mac80211 TXQs model
Move to use the new mac80211 TXQs implementation. This has
quite a few benefits for us. We can get rid of the awkward
mapping of DQA to mac80211 queues. We can stop buffering
traffic while waiting for the queue to be allocated. We can
also use mac80211 AMSDUs instead of building it ourselves.
The usage is pretty simple:
Each ieee80211_txq contains iwl_mvm_txq. There is such a
queue for each TID, and one for management frames. We keep
having static AP queues for probes and non-bufferable MMPDUs,
along with broadcast and multicast queues. Those are being
used from the "old" TX invocation path - iwl_mvm_mac_tx.
When there is a new frame in a TXQ, iwl_mvm_mac_wake_tx is
being called, and either invokes the TX path, or allocates
the queue if it does not exist.
Most of the TX path is left untouched, although we can consider
cleaning it up some more, for example get rid of the duplication
of txq_id in both iwl_mvm_txq and iwl_mvm_dqa_txq_info.
Signed-off-by: Sara Sharon <sara.sharon@intel.com>
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
Diffstat (limited to 'drivers/net/wireless/intel/iwlwifi/mvm/rs-fw.c')
0 files changed, 0 insertions, 0 deletions