From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: pxa: PXA270 D-Cache as ram
Date: Tue, 21 May 2013 17:00:20 +0200 [thread overview]
Message-ID: <201305211700.20807.marex@denx.de> (raw)
In-Reply-To: <1369137362.12900.13.camel@host5.omatika.ru>
Dear Sergey Yanovich,
> Dear Marek Vasut,
>
> On Tue, 2013-05-21 at 13:38 +0200, Marek Vasut wrote:
> > Yes, it's just an in-CPU RAM.
>
> Well, it is not 'just' RAM. It preserves its state during deep sleep and
> power off modes.
So does RAM during sleep state ;-)
> > > Anyway, SRAM preserves its state when power is off. Poweroff time could
> > > be in years with a backup battery. In addition, D-Cache is an order of
> > > magnitude faster than SRAM (approx. 9 times) for both reads and writes.
> >
> > Is there any measurable difference between using DCache and SRAM? Do you
> > have any evidence that a speedup happens?
>
> I haven't done any special profiling. I am just relying on PXA270 EMTS
> table 6-14. The table says SRAM reads take 9 cycles, writes take 7
> cycles. D-Cache operations take 1 cycle.
>
> > Still, the SRAM/DCache is only used until you leave board_init_f(), then
> > it's all DRAM.
>
> Yes, the patch as it is will only affects relocation speed and preserve
> SRAM from corruption.
Now this is the right (convincing) argument! What kind of corruption ? When does
it occur ?
> The speed gain can also be applied to uImage
> copying/unpacking, but that requires deeper understanding than I have at
> the moment.
Uh ... I lost you here. Can you please elaborate some more ?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-05-21 15:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 22:06 [U-Boot] [PATCH] arm: pxa: PXA270 D-Cache as ram Sergey Yanovich
2013-05-21 10:39 ` Marek Vasut
2013-05-21 10:42 ` Sergey Yanovich
2013-05-21 10:54 ` Marek Vasut
2013-05-21 11:23 ` Sergey Yanovich
2013-05-21 11:38 ` Marek Vasut
2013-05-21 11:56 ` Sergey Yanovich
2013-05-21 15:00 ` Marek Vasut [this message]
2013-05-21 16:31 ` Sergey Yanovich
2013-05-21 19:02 ` Marek Vasut
2013-05-21 19:18 ` Sergey Yanovich
2013-05-21 19:24 ` Marek Vasut
2013-05-21 19:42 ` Sergey Yanovich
2013-05-21 20:07 ` Marek Vasut
2013-05-21 20:24 ` Sergey Yanovich
2013-05-21 21:38 ` Marek Vasut
2013-05-22 13:02 ` Sergey Yanovich
2013-05-22 13:04 ` Marek Vasut
2013-05-22 13:21 ` Sergey Yanovich
2013-05-22 13:54 ` Marek Vasut
2013-05-23 17:43 ` Mike Dunn
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=201305211700.20807.marex@denx.de \
--to=marex@denx.de \
--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