From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Jerome Brunet <jbrunet@baylibre.com>,
linux-wireless@vger.kernel.org, MMC <linux-mmc@vger.kernel.org>,
AML <linux-amlogic@lists.infradead.org>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Kalle Valo <kvalo@kernel.org>, Eric Dumazet <edumazet@google.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>,
Alexander Prutskov <alep@cypress.com>,
Joseph chuang <jiac@cypress.com>,
Kevin Hilman <khilman@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@gmail.com>,
Angus Ainslie <angus@akkea.ca>,
Heiner Kallweit <hkallweit1@gmail.com>,
Pierre-Hugues Husson <phh@phh.me>
Subject: Re: Performance lower than expected with BCM4359/9 on S905X2
Date: Tue, 21 Mar 2023 13:37:40 +0100 [thread overview]
Message-ID: <ce0bd9a5-e44d-b30b-3434-9d5fd36e251a@free.fr> (raw)
In-Reply-To: <1jh6ue74x9.fsf@starbuckisacylon.baylibre.com>
On 21/03/2023 11:46, Jerome Brunet wrote:
> On Tue 21 Mar 2023 at 11:40, Marc Gonzalez wrote:
>
>> I've been benchmarking an Amlogic S905X2 board.
>> It provides a BCM4359/9 WiFi chip connected through SDIO.
>>
>> There's a large performance gap between vendor kernel and mainline.
>> (Downloading a 1GB file to /dev/null from a device inches away)
>
> The title is misleading. You are comparing different sources. This is
> not a regression. This is merely a difference.
I have changed the subject line to a (hopefully) more accurate one.
> If we are talking about mainline, then which board is it ? What is the
> corresponding DT ? What is the MMC configuration in both case ? Have
> you checked you are running with the same clock configuration to begin
> with ?
Perhaps my initial request was unclear, my apologies.
I was asking whether anyone using any S905X2 board had noticed
such a performance discrepancy. (Neil seems to have provided
a full explanation for the situation.)
For what it's worth, I'm using an sei530 board, which appears
to be a minor variant of the sei510 (down to the schematics).
>> # curl -o /dev/null http://192.168.1.254:8095/fixed/1G
>> % Total % Received % Xferd Average Speed Time Time Time Current
>> Dload Upload Total Spent Left Speed
>> 100 1024M 100 1024M 0 0 27.5M 0 0:00:37 0:00:37 --:--:-- 28.6M
>> vs
>> 100 1024M 100 1024M 0 0 11.0M 0 0:01:32 0:01:32 --:--:-- 11.0M
>>
>> Line 1 = vendor kernel (4.9.180 amlogic android)
>
> This cannot help identify a downstream kernel, and the infinite number
> of forks and patches associated with it.
I was not asking anyone to reproduce my exact setup.
I find it confusing that some assume there is something different
about the board I'm using. The more likely hypothesis is that all
S905X2 boards have the same behavior.
Regards
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2023-03-21 12:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 10:40 [Performance regression] " Marc Gonzalez
2023-03-21 10:46 ` Jerome Brunet
2023-03-21 12:37 ` Marc Gonzalez [this message]
2023-03-21 13:54 ` Performance lower than expected with " Jerome Brunet
2023-03-21 16:48 ` Marc Gonzalez
[not found] ` <EEE9FD80-C106-4A9B-AA8D-5C151E540CFD@hewittfamily.org.uk>
2023-04-04 16:09 ` [Performance regression] " Marc Gonzalez
2023-04-04 21:06 ` Martin Blumenstingl
2023-04-06 16:35 ` Marc Gonzalez
2023-04-06 17:07 ` Christian Hewitt
2023-04-06 17:41 ` Neil Armstrong
2023-04-17 14:22 ` Marc Gonzalez
2023-03-21 11:45 ` Neil Armstrong
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=ce0bd9a5-e44d-b30b-3434-9d5fd36e251a@free.fr \
--to=marc.w.gonzalez@free.fr \
--cc=alep@cypress.com \
--cc=angus@akkea.ca \
--cc=aspriel@gmail.com \
--cc=edumazet@google.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=hkallweit1@gmail.com \
--cc=jbrunet@baylibre.com \
--cc=jiac@cypress.com \
--cc=khilman@baylibre.com \
--cc=kvalo@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.blumenstingl@gmail.com \
--cc=neil.armstrong@linaro.org \
--cc=phh@phh.me \
--cc=pieter-paul.giesberts@broadcom.com \
--cc=ulf.hansson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®