From: David Brownell <david-b@pacbell.net>
To: Russ Dill <russ.dill@gmail.com>
Cc: David Hagood <david.hagood@gmail.com>, linux-omap@vger.kernel.org
Subject: Re: Benchmarking: POP flash vs. MMC?
Date: Sun, 5 Apr 2009 15:53:38 -0700 [thread overview]
Message-ID: <200904051553.38586.david-b@pacbell.net> (raw)
In-Reply-To: <f9d2a5e10904032116p4087be51o14efd360114d3d9f@mail.gmail.com>
On Friday 03 April 2009, Russ Dill wrote:
> On Fri, Apr 3, 2009 at 7:52 PM, David Hagood <david.hagood@gmail.com> wrote:
> > Well, that's not what I would have expected - I would have thought
> > reads on POP would have been faster than that, and cheaper - the SD
> > being the same speed but less CPU is surprising.
>
> The POP flash may not have a DMA ability.
ISTR it does, but it's not used. There are other speedups possible;
the NAND driver in the OMAP tree is pretty simplistic. It doesn't
use the "Prefetch and Write-Posting Engine" (we don't know if that
really helps though); or the more aggressive ECC support (4-bit and
8-bit modes both work).
Of course using DMA in the MTD stack can be a bit problematic in
general. It assumes that DMA is not used ... to the extent of not
guaranteeing to provide DMA-mappable I/O buffers.
That said, it's hard to achieve speedups through DMA for such small
blocks of memory ... an issue which is not unique to NAND.
> Also, the POP flash contents
> are compressed and ECC corrected, so its a lot of extra work for the
> CPU.
ECC is done in hardware for the native NAND stack on OMAP;
but you're right about compression.
Another point is that "managed NAND" (like MMC and eMMC, and
various SSD flavors) is there to offload some complicated
and error-prone tasks like wear-leveling.
next prev parent reply other threads:[~2009-04-05 22:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 21:24 Benchmarking: POP flash vs. MMC? david.hagood
2009-04-04 0:57 ` Russ Dill
2009-04-04 2:52 ` David Hagood
2009-04-04 4:16 ` Russ Dill
2009-04-05 22:53 ` David Brownell [this message]
2009-04-06 7:41 ` Artem Bityutskiy
2009-04-06 8:13 ` Russ Dill
2009-04-06 9:07 ` Artem Bityutskiy
2009-04-06 9:59 ` David Brownell
2009-04-06 10:08 ` Paul Walmsley
2009-04-06 10:23 ` David Brownell
2009-04-06 10:34 ` Paul Walmsley
2009-04-06 10:48 ` David Brownell
2009-04-07 17:22 ` Tony Lindgren
2009-04-07 12:09 ` Woodruff, Richard
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=200904051553.38586.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=david.hagood@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=russ.dill@gmail.com \
/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