mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Major memory performance decline from u-boot to barebox
Date: Mon, 08 Jul 2024 13:41:19 +0200	[thread overview]
Message-ID: <lybk38xg9s.fsf@ensc-pc.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <5c3923960eb059b2edc64a73cf53a75c5a28476c.camel@pengutronix.de> (Lucas Stach's message of "Mon, 08 Jul 2024 12:53:20 +0200")

Lucas Stach <l.stach@pengutronix.de> writes:

>> I have a karo tx6s module (imx6s, 512 MiB RAM) which is shipped with an
>> ancient u-boot 2015 bootloader.
>> 
>> barebox 2024.07 works out-of-the box on it. But under the booted linux
>> system a see a major regression in memory performance.
>
> The most likely cause is that Barebox applies the workaround for ARM
> erratum 845369, which has a major impact on streaming writes and thus
> both memset and memcpy performance. The old U-Boot probably does not
> include this workaround.
>
> You may check this theory by removing the call to
> enable_arm_errata_845369_war in imx6_cpu_lowlevel_init.

Thanks; after disabling this workaround, benchmarks are reporting high
numbers again.

Would it make sense to enable this workaround conditionally?  E.g. the
imx6s is not affected by this erratum because it has only one core and
no ACP.



Enrico



  reply	other threads:[~2024-07-08 11:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-08 10:22 Enrico Scholz
2024-07-08 10:53 ` Lucas Stach
2024-07-08 11:41   ` Enrico Scholz [this message]
2024-07-08 12:04     ` Lucas Stach

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=lybk38xg9s.fsf@ensc-pc.intern.sigma-chemnitz.de \
    --to=enrico.scholz@sigma-chemnitz.de \
    --cc=barebox@lists.infradead.org \
    --cc=l.stach@pengutronix.de \
    /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