From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Jes Sorensen <Jes.Sorensen@gmail.com>
Subject: RE: [PATCH v2 2/2] wifi: rtl8xxxu: Use a longer retry limit of 48
Date: Mon, 9 Jan 2023 01:36:58 +0000 [thread overview]
Message-ID: <0b70feb9ae7c423b816ffd778fe882fb@realtek.com> (raw)
In-Reply-To: <477d745b-6bac-111d-403c-487fc19aa30d@gmail.com>
> -----Original Message-----
> From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
> Sent: Sunday, January 8, 2023 11:08 PM
> To: linux-wireless@vger.kernel.org
> Cc: Jes Sorensen <Jes.Sorensen@gmail.com>; Ping-Ke Shih <pkshih@realtek.com>
> Subject: [PATCH v2 2/2] 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>
> ---
> v2:
> - Use Cc tag instead of Fixes.
> ---
> drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c | 9 ---------
> 1 file changed, 9 deletions(-)
>
> diff --git a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c
> b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c
> index 4c76fad67150..ab4074caf191 100644
> --- a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c
> +++ b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c
> @@ -6184,7 +6184,6 @@ static int rtl8xxxu_config(struct ieee80211_hw *hw, u32 changed)
> {
> struct rtl8xxxu_priv *priv = hw->priv;
> struct device *dev = &priv->udev->dev;
> - u16 val16;
> int ret = 0, channel;
> bool ht40;
>
> @@ -6194,14 +6193,6 @@ static int rtl8xxxu_config(struct ieee80211_hw *hw, u32 changed)
> __func__, hw->conf.chandef.chan->hw_value,
> changed, hw->conf.chandef.width);
>
> - if (changed & IEEE80211_CONF_CHANGE_RETRY_LIMITS) {
> - val16 = ((hw->conf.long_frame_max_tx_count <<
> - RETRY_LIMIT_LONG_SHIFT) & RETRY_LIMIT_LONG_MASK) |
> - ((hw->conf.short_frame_max_tx_count <<
> - RETRY_LIMIT_SHORT_SHIFT) & RETRY_LIMIT_SHORT_MASK);
> - rtl8xxxu_write16(priv, REG_RETRY_LIMIT, val16);
> - }
> -
> if (changed & IEEE80211_CONF_CHANGE_CHANNEL) {
> switch (hw->conf.chandef.width) {
> case NL80211_CHAN_WIDTH_20_NOHT:
> --
> 2.38.0
>
> ------Please consider the environment before printing this e-mail.
next prev parent reply other threads:[~2023-01-09 1:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 15:06 [PATCH v2 1/2] wifi: rtl8xxxu: Report the RSSI to the firmware Bitterblue Smith
2023-01-08 15:08 ` [PATCH v2 2/2] wifi: rtl8xxxu: Use a longer retry limit of 48 Bitterblue Smith
2023-01-09 1:36 ` Ping-Ke Shih [this message]
2023-01-09 1:36 ` [PATCH v2 1/2] wifi: rtl8xxxu: Report the RSSI to the firmware Ping-Ke Shih
2023-01-16 16:27 ` Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0b70feb9ae7c423b816ffd778fe882fb@realtek.com \
--to=pkshih@realtek.com \
--cc=Jes.Sorensen@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rtl8821cerfe2@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).