From: James Prestwood <prestwoj@gmail.com>
To: Alexandre Ferrieux <alexandre.ferrieux@gmail.com>,
linux-wireless@vger.kernel.org
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [RFC PATCH] mac80211: clip ADDBA instead of bailing out
Date: Wed, 19 Mar 2025 06:21:51 -0700 [thread overview]
Message-ID: <1560b292-6366-4588-ad4d-654377613b84@gmail.com> (raw)
In-Reply-To: <69c63a19-5419-4bbe-858f-6ca100345a28@orange.com>
Hi Alexandre,
On 3/19/25 3:58 AM, Alexandre Ferrieux wrote:
> When a Linux Wifi{4,5} device talks to a Wifi6 AP, if the AP proposes a Block
> Acknowledgement aggregation size (ADDBA) exceeding its expectations, the code in
> mac80211 just bails out, rejecting the aggregation. This yields a big
> performance penalty on the ack path, which is observable in comparison with
> other OSes (Windows and MacOS) which "play smarter" and accept the proposal with
> a "clipped" size.
Out of curiosity do you have any performance numbers for this, like
Linux vs Windows vs MacOS? We ran into a significant performance hit
after I added multicast RX support on ath10k (after ~30 clients were on
the same channel). After looking into the pcaps we saw many ADDBA
failures and ultimately had to disable multicast RX. I want to give this
patch a try either way, but I was curious if you had any data on
performance improvements.
>
> A typical scenario would be:
>
> AP -> Device : ADDBA_request(size=256)
>
> Current Linux reaction:
>
> Device -> AP : ADDBA_reply(failure)
>
> Other OSes reaction:
>
> Device -> AP : ADDBA_reply(size=64)
>
> Note that the IEEE802.11 standard allows for both reactions, but it sounds
> really suboptimal to be bailing out instead of clipping. The patch below does
> the latter.
>
> Signed-off-by: Alexandre Ferrieux <alexandre.ferrieux@gmail.com>
> ---
>
> diff --git a/net/mac80211/agg-rx.c b/net/mac80211/agg-rx.c
> index f3fbe5a4395e..264dad847842 100644
> --- a/net/mac80211/agg-rx.c
> +++ b/net/mac80211/agg-rx.c
> @@ -317,18 +317,20 @@ void __ieee80211_start_rx_ba_session(struct sta_info *sta,
> max_buf_size = IEEE80211_MAX_AMPDU_BUF_HT;
>
> /* sanity check for incoming parameters:
> - * check if configuration can support the BA policy
> - * and if buffer size does not exceeds max value */
> + * check if configuration can support the BA policy */
> /* XXX: check own ht delayed BA capability?? */
> if (((ba_policy != 1) &&
> - (!(sta->sta.deflink.ht_cap.cap & IEEE80211_HT_CAP_DELAY_BA))) ||
> - (buf_size > max_buf_size)) {
> - status = WLAN_STATUS_INVALID_QOS_PARAM;
> + (!(sta->sta.deflink.ht_cap.cap & IEEE80211_HT_CAP_DELAY_BA)))) {
> + status = WLAN_STATUS_INVALID_QOS_PARAM;
> ht_dbg_ratelimited(sta->sdata,
> "AddBA Req with bad params from %pM on tid
> %u. policy %d, buffer size %d\n",
> sta->sta.addr, tid, ba_policy, buf_size);
> goto end;
> }
> + if (buf_size > max_buf_size) {
> + buf_size = max_buf_size ; // Clip instead of bailing out
> + }
> +
> /* determine default buffer size */
> if (buf_size == 0)
> buf_size = max_buf_size;
>
>
next prev parent reply other threads:[~2025-03-19 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250317163902.1893378-1-sashal@kernel.org>
[not found] ` <20250317163902.1893378-2-sashal@kernel.org>
2025-03-19 10:58 ` [RFC PATCH] mac80211: clip ADDBA instead of bailing out Alexandre Ferrieux
2025-03-19 13:21 ` James Prestwood [this message]
2025-03-19 14:18 ` alexandre.ferrieux
2025-03-19 14:25 ` James Prestwood
2025-03-19 19:50 ` James Prestwood
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=1560b292-6366-4588-ad4d-654377613b84@gmail.com \
--to=prestwoj@gmail.com \
--cc=alexandre.ferrieux@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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