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



 
> Can you compare SHA256 instead and see if the difference is still as stark?
> Make sure that CONFIG_DIGEST_SHA256_ARM is enabled.
The SHA256 is enabled. SHA256 on a 1 MB file:
Barebox: 843ms
Linux: 
[root@openware]# time sha256sum /tmp/mtd0
eef67a3327e3eaa50ee7b1dad87901465f00d76a6308e360a2fedab82c79f493  /tmp/mtd0

real    0m0.059s
user    0m0.056s
sys     0m0.001s

On another note, the boot loader using the LS1021A is much slower than using the PPC P1014.
I compare those two as we used the LS1021A as a replacement for P1014 on a board (same peripherals, same boot sequence)
The P1014 reach the prompt in 200ms while the LS1021 takes 700ms.

Also, I noticed that the pageflags is different for the DDR memory on Barebox and Linux as seen by the Lauterbach:
Barebox: write-back/no allocate
Linux : Inner:write-back/allocate outer: write-back/allocate
Could that mean the L2 cache Is not used?
> 
> Do barebox and Linux run at the same CPU frequency?
According to the Lauterbach, clock ratio have not changed in the clocking registers
> 
> Cheers,
> Ahmad
> 
> >
> > Cheers,
> > Renaud
> >
> >
> >
> >
> 
> --
> Pengutronix e.K.                           |                             |
> Steuerwalder Str. 21                       |
> https://urldefense.com/v3/__http://www.pengutronix.de/__;!!HKOSU0g!D
> 4uFepgqngTTHamr_7tlQeQoRJqSLL8npxTFBWFF-
> kjpZuHgzi1quS6EE1ecjCKr_O_FJGPfkAnWXQyfONKJxqgrtQQ$   |
> 31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |


  reply	other threads:[~2023-03-30 13:33 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
2023-03-30 13:31   ` Renaud Barbier [this message]
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=BL0PR07MB566562459F73E606BF3BB629EC8E9@BL0PR07MB5665.namprd07.prod.outlook.com \
    --to=renaud.barbier@ametek.com \
    --cc=a.fatoum@pengutronix.de \
    --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