From: Artem Bityutskiy <dedekind@yandex.ru>
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: Mon, 06 Apr 2009 12:07:01 +0300 [thread overview]
Message-ID: <49D9C635.4040000@yandex.ru> (raw)
In-Reply-To: <f9d2a5e10904060113g37c3dd7fk5be6d3a12ab169c4@mail.gmail.com>
Russ Dill wrote:
> On Mon, Apr 6, 2009 at 12:41 AM, Artem Bityutskiy <dedekind@yandex.ru> wrote:
>> David Hagood 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.
>> 1. As Russ and David said, OneNAND driver does not really
>> use DMA, because the I/O is done in 2K chunks, and this
>> is just too small piece of data for DMA.
>
> All very relevant, but just to avoid confusion; the tests were
> performed on a Beagleboard with 256MB of Micron NAND.
Ok, sorry. The CRC part should be relevant.
The bulk_read part may also be relevant if your HW is
able to read multiple NAND pages faster than reading
them one-by-one. The compression links should be
helpful for compressor selection.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-04-06 9:07 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
2009-04-06 7:41 ` Artem Bityutskiy
2009-04-06 8:13 ` Russ Dill
2009-04-06 9:07 ` Artem Bityutskiy [this message]
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=49D9C635.4040000@yandex.ru \
--to=dedekind@yandex.ru \
--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