From: Jun Nie <jun.nie@linaro.org>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: kvalo@kernel.org, quic_periyasa@quicinc.com,
quic_kangyang@quicinc.com, ath12k@lists.infradead.org,
Neil Armstrong <neil.armstrong@linaro.org>
Subject: Re: Performance of WCN7850
Date: Mon, 25 Mar 2024 23:08:17 +0800 [thread overview]
Message-ID: <CABymUCM9fSG=Mh1AFiAy-sWqtUH8_spnY=x6FiSTK3MbWPc32A@mail.gmail.com> (raw)
In-Reply-To: <91902c69-6a51-43f9-8124-7b19c4265b22@quicinc.com>
Jeff Johnson <quic_jjohnson@quicinc.com> 于2024年3月12日周二 01:23写道：
>
> On 3/11/2024 2:19 AM, Jun Nie wrote:
> > The latest finding is that 6GHz TX performance of wcn7850 is as we talked about.
> > But the RX performance wcn7850 is better than 5GHz case. So the direction
> > impacts a lot. Not sure whether the bottoleneck is in scheduling side, or any
> > configuration on TX power.
>
> There is at least one 6 GHz patch in the pipeline that should be posted this week.
>
> /jeff
>
Hi Jeff,
What's the performance data with the patch in the pipeline? Is it
possible to have a
early test with my hardware?
Jun
prev parent reply other threads:[~2024-03-25 15:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 13:54 Performance of WCN7850 Jun Nie
2024-02-27 15:23 ` Jeff Johnson
2024-02-28 8:52 ` Jun Nie
2024-02-28 17:39 ` Jeff Johnson
2024-02-28 17:43 ` Jeff Johnson
2024-02-29 15:52 ` Jeff Johnson
2024-03-01 9:14 ` 6GHz AP association failure on WCN7850 Jun Nie
2024-03-01 11:42 ` Kang Yang
2024-03-04 10:14 ` Jun Nie
2024-03-05 8:30 ` Kang Yang
2024-03-06 2:25 ` Jun Nie
2024-03-06 6:45 ` Kang Yang
2024-03-06 14:49 ` Jun Nie
2024-03-04 8:42 ` Kalle Valo
[not found] ` <CABymUCN0c9HK3vC3ZFxfXkV9Ezcqwq41J4vGSkpsz09sMDL8rw@mail.gmail.com>
2024-03-11 9:19 ` Performance of WCN7850 Jun Nie
2024-03-11 17:21 ` Jeff Johnson
2024-03-25 15:08 ` Jun Nie [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='CABymUCM9fSG=Mh1AFiAy-sWqtUH8_spnY=x6FiSTK3MbWPc32A@mail.gmail.com' \
--to=jun.nie@linaro.org \
--cc=ath12k@lists.infradead.org \
--cc=kvalo@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_jjohnson@quicinc.com \
--cc=quic_kangyang@quicinc.com \
--cc=quic_periyasa@quicinc.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 read-only IMAP folder(s) and NNTP newsgroup(s).