From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Kalle Valo <kvalo@kernel.org>
Subject: RE: [PATCH] wifi: rtw88: Fix the RX aggregation in USB 3 mode
Date: Wed, 9 Oct 2024 00:18:30 +0000 [thread overview]
Message-ID: <3731c7452dbf48f8a35e982d08963ba8@realtek.com> (raw)
In-Reply-To: <afb94a82-3d18-459e-97fc-1a217608cdf0@gmail.com>
Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> RTL8822CU, RTL8822BU, and RTL8821CU don't need BIT_EN_PRE_CALC.
> In fact, RTL8822BU in USB 3 mode doesn't pass all the frames to the
> driver, resulting in much lower download speed than normal:
Have you also tested in USB 2 mode? Just want to know this patch works on
both modes.
> [ 5] 0.00-10.00 sec 98.6 MBytes 82.7 Mbits/sec receiver
>
> Don't set BIT_EN_PRE_CALC. Then the speed is much better:
>
> [ 5] 0.00-10.00 sec 714 MBytes 599 Mbits/sec receiver
Good job. That improves ten times of RX throughput!
>
> Fixes: 002a5db9a52a ("wifi: rtw88: Enable USB RX aggregation for 8822c/8822b/8821c")
> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
Acked-by: Ping-Ke Shih <pkshih@realtek.com>
> ---
> The code in the official drivers is a little broken. It sets
> BIT_EN_PRE_CALC and then immediately unsets it. I didn't notice that
> before.
>
> Maybe this should go to kernel 6.12, if it's not too late. Commit 002a5db9a52a
> ("wifi: rtw88: Enable USB RX aggregation for 8822c/8822b/8821c") first appears
> in 6.12.
Kalle, could you help to take this patch via wireless tree? If yes, I will
assign this to you in patchwork.
next prev parent reply other threads:[~2024-10-09 0:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 18:44 [PATCH] wifi: rtw88: Fix the RX aggregation in USB 3 mode Bitterblue Smith
2024-10-09 0:18 ` Ping-Ke Shih [this message]
2024-10-09 16:11 ` Bitterblue Smith
2024-10-11 11:56 ` Kalle Valo
2024-10-11 12:48 ` Ping-Ke Shih
2024-10-11 13:44 ` Kalle Valo
2024-10-17 14:24 ` Kalle Valo
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=3731c7452dbf48f8a35e982d08963ba8@realtek.com \
--to=pkshih@realtek.com \
--cc=kvalo@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).