From: Ping-Ke Shih <pkshih@realtek.com>
To: Adilson <aoleandro@proton.me>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: wifi: rtw89: 8852AE: zero SMA in addr CAM for virtual monitor vif, and ~200 ms delay before first TX attempt of injected unicast
Date: Mon, 5 Oct 2026 02:16:30 +0000 [thread overview]
Message-ID: <d869d864b8fa40c683829d49c23e2291@realtek.com> (raw)
In-Reply-To: <b41nlcULR-r_hxbVG6EOsjESlvS4yT_ArYlWgP26g34UKbdoMRoLxMd2pLl4h0L6sB1GOAGr2pT2ofsCRXAcJSqm4lxEWIwH4gTZbjFVmiI=@proton.me>
Adilson <aoleandro@proton.me> wrote:
> Would a patch along these lines be acceptable upstream? And would it
> be enough for, or a step towards, advertising ACTIVE_MONITOR on these
> chips? The fix could also key on addr_valid instead of testing for a
> zero address, if you prefer.
I think advertising NL80211_FEATURE_ACTIVE_MONITOR to support active
monitor is better way.
>
> 2) Injected unicast waits ~200 ms before the first TX attempt
>
> Injected unicast data frames reach the peer much later than injected
> multicast. Your series from November 2025 (rate/bw/GI for injected
> packets) is included in this kernel; it does not seem to touch this
> wait.
The main differences from unicast and multicast frames are:
1. hw queue
2. with different queue. It relies on EDCA parameter.
3. rate
You can adjust unicast frame to TX with the same desc_info attributes
as multicast frame to see if anything improved.
> Disclosure: I did this investigation with the help of an AI assistant
> (Claude, by Anthropic), which I used to read the driver code, write the
> measurement scripts and the experimental patches, and draft this
> message. All measurements were run by me on my own hardware, and I
> have reviewed every claim above and can answer questions about it.
Understood. Currently I assume long long article is generated by LLM.
I knew that becomes common, but it is actual heavy load to me to
read a lot. But still noted your disclosure.
prev parent reply other threads:[~2026-10-05 2:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 2:49 wifi: rtw89: 8852AE: zero SMA in addr CAM for virtual monitor vif, and ~200 ms delay before first TX attempt of injected unicast Adilson
2026-10-05 2:16 ` Ping-Ke Shih [this message]
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=d869d864b8fa40c683829d49c23e2291@realtek.com \
--to=pkshih@realtek.com \
--cc=aoleandro@proton.me \
--cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.