From: Johannes Berg <johannes@sipsolutions.net>
To: Remi Pommarel <repk@triplefau.lt>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Pablo MARTIN-GOMEZ <pmartin-gomez@freebox.fr>
Subject: Re: [PATCH wireless] wifi: mac80211: Fix ADDBA update when HW supports reordering
Date: Mon, 23 Feb 2026 12:50:28 +0100 [thread overview]
Message-ID: <0f0703e2749185f9a334b3435ffe247b42e6923b.camel@sipsolutions.net> (raw)
In-Reply-To: <aZsmk0lUpL0UBd6Q@pilgrim>
On Sun, 2026-02-22 at 17:06 +0100, Remi Pommarel wrote:
> > > That does make sense. However, if I understand correctly, it means that
> > > even if we end up storing the timeout for drivers that support
> > > reordering, a new IEEE80211_AMPDU_RX_UPDATE should still be introduced,
> > > right?
> >
> > I guess in order to do a no-op update that doesn't change the timeout,
> > we could? But not sure it's all worth it?
>
> I was going to say it would not be a no-op for a buf_size update but,
> if I understand correctly, even when SUPPORTS_REORDERING_BUFFER is not
> set the buf_size update is ignored completely and the reorder_buf is
> not resized yet a successful addba response is sent. Don't we need to
> check for buf_size change as well as timeout also?
I was going to say that I thought buf_size is not allowed to change, but
(re)reading the spec doesn't seem to bear that out.
I guess we could just unconditionally reject any updates. I'm not sure
now why we ever added the update in the first place. Perhaps some
implementation was doing no-op updates and failing on negative
responses?
> > Pablo seems to have looked up that it _is_ supported - which I didn't
> > expect because it's not part of the API contract, so the drivers
> > implemented something that can't actually ever get hit? Seems odd. And
> > I'm pretty sure e.g. iwlwifi wouldn't support it.
> >
> > But I basically also think it's not worth it in practice; why try to
> > support something that's never going to happen?
>
> Just to confirm, you mean that updating the timeout is not worth it, but
> fixing this issue is still needed right?
Right.
johannes
next prev parent reply other threads:[~2026-02-23 11:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 10:36 Remi Pommarel
2026-02-17 11:30 ` Johannes Berg
2026-02-17 13:05 ` Remi Pommarel
2026-02-17 13:59 ` Johannes Berg
2026-02-17 14:38 ` Remi Pommarel
2026-02-17 16:00 ` Johannes Berg
2026-02-22 16:06 ` Remi Pommarel
2026-02-23 11:50 ` Johannes Berg [this message]
2026-02-23 13:25 ` Pablo MARTIN-GOMEZ
2026-02-26 15:49 ` Remi Pommarel
2026-02-26 16:28 ` Johannes Berg
2026-02-17 15:30 ` Pablo MARTIN-GOMEZ
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=0f0703e2749185f9a334b3435ffe247b42e6923b.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pmartin-gomez@freebox.fr \
--cc=repk@triplefau.lt \
/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
all inboxes | Powered by JetHome®