diff options
| author | Stanislaw Gruszka <sgruszka@redhat.com> | 2013-10-18 11:36:54 +0200 |
|---|---|---|
| committer | John W. Linville <linville@tuxdriver.com> | 2013-10-18 13:41:11 -0400 |
| commit | 36165fd5b00bf8163f89c21bb16a3e9834555b10 (patch) | |
| tree | 666b0e1b64584cd684e0e8c3d06f32c380cc4a69 /drivers/net/wireless/b43/phy_n.c | |
| parent | 5671ab05cf2a579218985ef56595387932d78ee4 (diff) | |
| download | talos-op-linux-36165fd5b00bf8163f89c21bb16a3e9834555b10.tar.gz talos-op-linux-36165fd5b00bf8163f89c21bb16a3e9834555b10.zip | |
rt2800usb: slow down TX status polling
Polling TX statuses too frequently has two negative effects. First is
randomly peek CPU usage, causing overall system functioning delays.
Second bad effect is that device is not able to fill TX statuses in
H/W register on some workloads and we get lot of timeouts like below:
ieee80211 phy4: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 7 in queue 2
ieee80211 phy4: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 7 in queue 2
ieee80211 phy4: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping
This not only cause flood of messages in dmesg, but also bad throughput,
since rate scaling algorithm can not work optimally.
In the future, we should probably make polling interval be adjusted
automatically, but for now just increase values, this make mentioned
problems gone.
Resolve:
https://bugzilla.kernel.org/show_bug.cgi?id=62781
Cc: stable@vger.kernel.org
Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers/net/wireless/b43/phy_n.c')
0 files changed, 0 insertions, 0 deletions
