From: Lukasz Majewski <l.majewski@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Performance of the ARM's PL310 L2 cache.
Date: Fri, 17 Aug 2012 17:49:53 +0200 [thread overview]
Message-ID: <20120817174953.08add23e@amdc308.digital.local> (raw)
Hi Aneesh,
I've enabled the L2 cache for Trats board. Please find results from
performance tests.
The test function as well as my way for enabling L2 are attached to
this e-mail.
I simply left the default configuration (number of ways, associativity)
as it is at Linux Kernel's driver.
Results:
test_l2_cache() performed once:
L1 L2 TIME [seconds]
OFF OFF 90,359
ON OFF 62,236
ON ON 61,687
L1 speedup: ~33 %
L2 speedup (when compared to L1): < 1%
test_l2_cache() performed 5000 times:
L1 L2 TIME [seconds]
OFF OFF 444,9
ON OFF 320,55
ON ON 287,21
L1 speedup: ~28 %
L2 speedup (when compared to L1): ~ 10%
Normal u-boot operation (from system startup - up till passing
execution to kernel).
L1 L2 TIME [seconds]
OFF OFF 1,813
ON OFF 1,552
ON ON 1,533
As one can observe, for normal u-boot operation there is no significant
difference.
Have you had similar results with OMAP?
Do you do more configuration when enabling the L2 at OMAP?
The assembly code presented below (armv7/omap-common/lowlevel_init.S)
puzzles me a bit...
ENTRY(set_pl310_ctrl_reg)
LDR r12, =0x102 @ Set PL310 control register - value in R0
.word 0xe1600070 @ SMC #0 - hand assembled
@because -march=armv5
@ call ROM Code API to set control
@ register
ENDPROC(set_pl310_ctrl_reg)
Are there any special operations executed@"ROM Code API"?
--
Best regards,
Lukasz Majewski
Samsung Poland R&D Center | Linux Platform Group
next reply other threads:[~2012-08-17 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 15:49 Lukasz Majewski [this message]
2012-08-17 19:09 ` [U-Boot] Performance of the ARM's PL310 L2 cache Tom Rini
2012-09-23 20:12 ` Marek Vasut
2012-10-01 8:23 ` Lukasz Majewski
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=20120817174953.08add23e@amdc308.digital.local \
--to=l.majewski@samsung.com \
--cc=u-boot@lists.denx.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