From: Ping-Ke Shih <pkshih@realtek.com>
To: Ezra Buehler <ezra@easyb.ch>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Jes Sorensen <Jes.Sorensen@gmail.com>,
Kalle Valo <kvalo@kernel.org>,
Martin Kaistra <martin.kaistra@linutronix.de>,
Bitterblue Smith <rtl8821cerfe2@gmail.com>,
Johannes Berg <johannes.berg@intel.com>,
"Reto Schneider" <reto.schneider@husqvarnagroup.com>,
Ezra Buehler <ezra.buehler@husqvarnagroup.com>
Subject: RE: [PATCH v1 0/3] wifi: rtl8xxxu: AP mode fixes (for gen1 devices)
Date: Thu, 26 Jun 2025 00:37:42 +0000 [thread overview]
Message-ID: <5b31bd2ce9274d1380f210cb0b6b79c3@realtek.com> (raw)
In-Reply-To: <8132EC31-A53A-4C49-93D6-70D45600C4B4@easyb.ch>
Ezra Buehler <ezra@easyb.ch> wrote:
> > On 19 Feb 2025, at 18:52, Ezra Buehler <ezra@easyb.ch> wrote:
> >
> > From: Ezra Buehler <ezra.buehler@husqvarnagroup.com>
> >
> > As mentioned in the previous patch [1], especially the transmit rate is
> > rather low in AP mode with gen1 devices like the RTL8192CU. The
> > following changes seem to fix the issue.
> >
> > When looking at the patches introducing the initial AP support [2], I
> > noticed that rtl8xxxu_gen2_report_connect() was altered too. So, now I
> > am wondering if we need to use `macid` and `role` in
> > rtl8xxxu_gen1_report_connect() as well...
> >
> > [1]: https://lore.kernel.org/all/20250122071512.10165-1-ezra@easyb.ch/
> > [2]: https://lore.kernel.org/all/20230428150833.218605-1-martin.kaistra@linutronix.de/
> >
> >
> > Ezra Buehler (3):
> > wifi: rtl8xxxu: Use macid in rtl8xxxu_update_rate_mask()
> > wifi: rtl8xxxu: Use macid in rtl8xxxu_fill_txdesc_v1()
> > wifi: rtl8xxxu: Make sure TX rate is reported in AP mode
> >
> > drivers/net/wireless/realtek/rtl8xxxu/core.c | 28 ++++++++++++++++++-
> > .../net/wireless/realtek/rtl8xxxu/rtl8xxxu.h | 1 +
> > 2 files changed, 28 insertions(+), 1 deletion(-)
> >
> > —
> > 2.43.0
>
> I apologize for the radio silence. It turned out that these changes do
> not improve things. I must have made a mistake when measuring throughput
> back then.
>
> When testing the TX rate (with iperf3), I see the throughput constantely
> dropping to 0 bits/sec. This makes AP mode unusable even for our
> non-data-heavy use case.
>
> Do you have any suggestions where to dig deeper to get to the bottom of
> this?
Testing with single one station connected would be easier to address problem,
and ensure mac_id is always 1 for AP mode transmitting packets to the
station.
Also, you need a sniffer to check PHY rate if it can keep. As well as the
rate when throughput dropped. If rate is good, check any misbehavior of air
packets.
Before all above, please ensure the PHY rate is good when it plays as a
station mode.
prev parent reply other threads:[~2025-06-26 0:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 17:52 [PATCH v1 0/3] wifi: rtl8xxxu: AP mode fixes (for gen1 devices) Ezra Buehler
2025-02-19 17:52 ` [PATCH v1 1/3] wifi: rtl8xxxu: Use macid in rtl8xxxu_update_rate_mask() Ezra Buehler
2025-02-20 5:58 ` Ping-Ke Shih
2025-02-19 17:52 ` [PATCH v1 2/3] wifi: rtl8xxxu: Use macid in rtl8xxxu_fill_txdesc_v1() Ezra Buehler
2025-02-20 6:00 ` Ping-Ke Shih
2025-02-19 17:52 ` [PATCH v1 3/3] wifi: rtl8xxxu: Make sure TX rate is reported in AP mode Ezra Buehler
2025-02-20 6:10 ` Ping-Ke Shih
2025-02-20 23:28 ` [PATCH v1 0/3] wifi: rtl8xxxu: AP mode fixes (for gen1 devices) Bitterblue Smith
2025-06-25 18:07 ` Ezra Buehler
2025-06-26 0:37 ` 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=5b31bd2ce9274d1380f210cb0b6b79c3@realtek.com \
--to=pkshih@realtek.com \
--cc=Jes.Sorensen@gmail.com \
--cc=ezra.buehler@husqvarnagroup.com \
--cc=ezra@easyb.ch \
--cc=johannes.berg@intel.com \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.kaistra@linutronix.de \
--cc=reto.schneider@husqvarnagroup.com \
--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).