mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Renaud Barbier <Renaud.Barbier@ametek.com>,
	Barebox List <barebox@lists.infradead.org>
Subject: Re: LS1021A performance
Date: Thu, 30 Mar 2023 13:45:39 +0200	[thread overview]
Message-ID: <9b5975a7-8b1d-0861-ce01-9206a3ddfc7d@pengutronix.de> (raw)
In-Reply-To: <BL0PR07MB5665003604A904B8AFBEB466EC8E9@BL0PR07MB5665.namprd07.prod.outlook.com>

Hello Renaud,


On 30.03.23 13:34, Renaud Barbier wrote:
> Hello,
> I am looking into the performance of the LS1021A between Linux and Barebox and a PPC P1014

> On Linux:
> [root@openware]# time md5sum /tmp/mtd0
> 26d8158619e5791859519654557aeeba  /tmp/mtd0
> 
> real    0m0.029s
> user    0m0.025s
> sys     0m0.001s
> 
> This is almost a 20 fold difference.
> 
> From my In-Circuit-Emulator, the cache is enabled on both Linux and Barebox. My guess it that it comes down how the MMU is used.
> Any input on how to speed up the boot loader would be appreciated.

Can you compare SHA256 instead and see if the difference is still as stark?
Make sure that CONFIG_DIGEST_SHA256_ARM is enabled.

Do barebox and Linux run at the same CPU frequency?

Cheers,
Ahmad

> 
> Cheers,
> Renaud
> 
> 
> 
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |




  reply	other threads:[~2023-03-30 11:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 11:34 Renaud Barbier
2023-03-30 11:45 ` Ahmad Fatoum [this message]
2023-03-30 13:31   ` Renaud Barbier
2023-03-30 14:17     ` Lucas Stach
2023-03-30 15:17       ` Renaud Barbier

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=9b5975a7-8b1d-0861-ce01-9206a3ddfc7d@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=Renaud.Barbier@ametek.com \
    --cc=barebox@lists.infradead.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