From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH rtw-next 0/5] wifi: rtw88: pci: Support an older design, like RTL8821AE/RTL8812AE
Date: Fri, 30 Oct 2026 00:43:02 +0000 [thread overview]
Message-ID: <08b040fc2f7e4311aa7721cf4969896f@realtek.com> (raw)
In-Reply-To: <ca4921aa-c8aa-4f88-880a-bc717aa103d4@gmail.com>
Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> >>>>
> >>>> It uses RX descriptor number 511, then number 0, then it doesn't
> >>>> want to use number 1 for "a while". It raises IMR_RDU once or twice,
> >>>> and only then it moves on to number 1, 2...
> >>>>
> >>>> Usually when it raises IMR_RDU there are 510 or 511 RX descriptors
> >>>> available (out of 512), so it has no excuse.
> >>>>
> >>>> Once it has raised IMR_RDU the RX speed doesn't exceed 70-100 Mbps
> >>>> anymore.
> >>>
> >>> If driver can receive packets on time, how does it raise ISR_RDU?
> >>
> >> It's a mystery for me.
> >>
> >>> Is RX interrupt triggered on time?
> >>>
> >>
> >> I'm not sure how to check this. I assume it is triggered on time because
> >> the ring was always nearly empty when it raised IMR_RDU.
> >
> > If interrupt handler can handle (ignore) "empty" RX ring , it might be harmless
> > to see raised IMR_RDU, right?
>
> It is harmless in the sense that everything keeps working, just the RX
> speed is low.
Have you dug the cause RX speed is low? The PHY rate becomes low at that time?
Or can air capture see any weird packets? Or did you think PCIE get stuck
somehow?
prev parent reply other threads:[~2026-10-30 0:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 22:57 [PATCH rtw-next 0/5] wifi: rtw88: pci: Support an older design, like RTL8821AE/RTL8812AE Bitterblue Smith
2026-10-23 22:59 ` [PATCH rtw-next 1/5] wifi: rtw88: Pass RX buffer to rtw_rx_query_rx_desc() Bitterblue Smith
2026-10-23 23:00 ` [PATCH rtw-next 2/5] wifi: rtw88: Pass TX descriptor to rtw_tx_fill_tx_desc() Bitterblue Smith
2026-10-23 23:01 ` [PATCH rtw-next 3/5] wifi: rtw88: pci: Introduce struct rtw_pci_gen Bitterblue Smith
2026-10-24 8:41 ` Luka Gejak
2026-10-28 21:26 ` Bitterblue Smith
2026-10-23 23:02 ` [PATCH rtw-next 4/5] wifi: rtw88: pci: Add functions to support older chips Bitterblue Smith
2026-10-24 8:36 ` Luka Gejak
2026-10-28 17:40 ` Bitterblue Smith
2026-10-23 23:05 ` [PATCH rtw-next 5/5] wifi: rtw88: pci: Handle more RX interrupts for RTL8821AE Bitterblue Smith
2026-10-27 1:52 ` [PATCH rtw-next 0/5] wifi: rtw88: pci: Support an older design, like RTL8821AE/RTL8812AE Ping-Ke Shih
2026-10-27 7:25 ` Luka Gejak
2026-10-27 8:07 ` Ping-Ke Shih
2026-10-28 17:41 ` Bitterblue Smith
2026-10-29 0:51 ` Ping-Ke Shih
2026-10-29 1:29 ` Ping-Ke Shih
2026-10-29 21:00 ` Bitterblue Smith
2026-10-30 0:43 ` 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=08b040fc2f7e4311aa7721cf4969896f@realtek.com \
--to=pkshih@realtek.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