diff options
| author | Bitterblue Smith <rtl8821cerfe2@gmail.com> | 2023-01-08 17:08:16 +0200 |
|---|---|---|
| committer | Kalle Valo <kvalo@kernel.org> | 2023-01-16 18:27:05 +0200 |
| commit | 2a86aa9a1892d60ef2e3f310f5b42b8b05546d65 (patch) | |
| tree | 0e5591b16551bb7a3624aa03bebadf0170dce2a3 /kernel/locking/rtmutex_api.c | |
| parent | 3922dc9fbdb8b090c5a973a6f2bd0e4cca81f821 (diff) | |
| download | linux-2a86aa9a1892d60ef2e3f310f5b42b8b05546d65.tar.gz linux-2a86aa9a1892d60ef2e3f310f5b42b8b05546d65.tar.bz2 linux-2a86aa9a1892d60ef2e3f310f5b42b8b05546d65.zip | |
wifi: rtl8xxxu: Use a longer retry limit of 48
The Realtek rate control algorithm goes back and forth a lot between
the highest and the lowest rate it's allowed to use. This is due to
a lot of frames being dropped because the retry limits set by
IEEE80211_CONF_CHANGE_RETRY_LIMITS are too low. (Experimentally, they
are 4 for long frames and 7 for short frames.)
The vendor drivers hardcode the value 48 for both retry limits (for
station mode), which makes dropped frames very rare and thus the rate
control is more stable.
Because most Realtek chips handle the rate control in the firmware,
which can't be modified, ignore the limits set by
IEEE80211_CONF_CHANGE_RETRY_LIMITS and use the value 48 (set during
chip initialisation), same as the vendor drivers.
Cc: stable@vger.kernel.org
Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
Reviewed-by: Ping-Ke Shih <pkshih@realtek.com>
Signed-off-by: Kalle Valo <kvalo@kernel.org>
Link: https://lore.kernel.org/r/477d745b-6bac-111d-403c-487fc19aa30d@gmail.com
Diffstat (limited to 'kernel/locking/rtmutex_api.c')
0 files changed, 0 insertions, 0 deletions