From: Nick Thompson <nick.thompson@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH RFC] NAND: Improve read performance from Large Page NAND devices
Date: Wed, 09 Dec 2009 11:43:44 +0000 [thread overview]
Message-ID: <4B1F8D70.5070105@ge.com> (raw)
In-Reply-To: <20091209110222.2AC613F6CC@gemini.denx.de>
On 09/12/09 11:02, Wolfgang Denk wrote:
> Dear Nick Thompson,
>
> In message <4B1E71D9.6080802@ge.com> you wrote:
>> Improve read performance from Large Page NAND devices.
>>
>> This patch produces a ~31% improvement in oob_first read speed (on a
>> 300MHz ARM9). The time for a mid-buffer 2k page read is now 293us,
>> 6.99MB/s (was 385us, 5.31MB/s). oob_first is probably the best case
>> improvement.
>>
>> Signed-off-by: Nick Thompson <nick.thompson@ge.com>
>
> Also tested on Canyonlands (460EX); here I actually see a slightj
> improvement (5.5% faster, i. e. time to read 126 MB from NAND goes
> down from 28.8 to 27.2 seconds (4.4 -> 4.6 MiB/s).
>
> Tested-by: Wolfgang Denk <wd@denx.de>
Hi Wolfgang,
Thanks again.
It seems the raw page data transfer rate is quite low on that board.
The patch saves time between page data transfers, so the percentage
improvement seen is better if you can get the page data out quicker.
The default read_buf (and write_buf) in nand_base.c are safe, but slow.
I put in davinci specific optimised versions (DMA or multibyte read
ticks might be used) to double my raw transfer rate. Without that, my
measurements would show ~15% improvement only.
In total on da830evm I'm getting a >300% speed improvement. 1.69MB/s
changes to 6.99MB/s. (5.31MB/s without this patch.)
Nick.
next prev parent reply other threads:[~2009-12-09 11:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 15:33 [U-Boot] [PATCH RFC] NAND: Improve read performance from Large Page NAND devices Nick Thompson
2009-12-08 22:06 ` Wolfgang Denk
2009-12-09 9:43 ` Nick Thompson
2009-12-09 11:02 ` Wolfgang Denk
2009-12-09 11:43 ` Nick Thompson [this message]
2010-01-16 1:51 ` Josh Gelinske
2010-01-18 12:48 ` Nick Thompson
2010-01-18 15:16 ` Josh Gelinske
-- strict thread matches above, loose matches on Subject: below --
2009-11-25 13:57 Nick Thompson
2009-12-01 0:55 ` Scott Wood
2009-12-01 10:13 ` Nick Thompson
2009-12-01 11:34 ` Nick Thompson
2009-12-01 18:43 ` Scott Wood
2009-12-01 18:38 ` Scott Wood
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=4B1F8D70.5070105@ge.com \
--to=nick.thompson@ge.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