From: Wolfgang Denk <wd@denx.de>
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 12:02:22 +0100 [thread overview]
Message-ID: <20091209110222.2AC613F6CC@gemini.denx.de> (raw)
In-Reply-To: <20091208220602.8796A19F3F@gemini.denx.de>
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>
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Any time things appear to be going better, you have overlooked some-
thing.
next prev parent reply other threads:[~2009-12-09 11:02 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 [this message]
2009-12-09 11:43 ` Nick Thompson
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=20091209110222.2AC613F6CC@gemini.denx.de \
--to=wd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.