From: Artem Bityutskiy <dedekind@yandex.ru>
To: David Hagood <david.hagood@gmail.com>
Cc: Russ Dill <russ.dill@gmail.com>, linux-omap@vger.kernel.org
Subject: Re: Benchmarking: POP flash vs. MMC?
Date: Mon, 06 Apr 2009 10:41:14 +0300 [thread overview]
Message-ID: <49D9B21A.2000002@yandex.ru> (raw)
In-Reply-To: <1238813563.12072.4.camel@surfer>
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.
2. UBIFS also compresses data on-the-flight. You may try
disabling it and see what changes, but probably not
too much, because of the way the driver writes (no DMA).
Try mounting with 'compre=none' option, see here:
http://www.linux-mtd.infradead.org/doc/ubifs.html#L_mountopts
BTW, some compression testing results may be found here:
http://www.linux-mtd.infradead.org/misc/misc.html#L_ubifs_compr
although they are not 100% relevant for this case.
3. UBIFS provides you greater data reliability. E.g., it
CRCs all data (see here
http://www.linux-mtd.infradead.org/doc/ubifs.html#L_checksumming)
OneNAND was very reliable last time we tested it, and we
disable _some_ CRC checking for it. Try to use the
'no_chk_data_crc' and get better read speed.
4. UBIFS has 'bulk read' feature which works well on OneNAND,
(see here: http://www.linux-mtd.infradead.org/doc/ubifs.html#L_readahead)
Try to enable it as well. You should end up with faster
read speed.
5. Last but not least, UBIFS+OneNAND provides just another
level of reliability, comparing to SD. In general, SDs are
not very good for storing system libraries, etc. I tried to
summarize this at some point here:
http://www.linux-mtd.infradead.org/doc/ubifs.html#L_raw_vs_ftl
HTH.
--
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 7:41 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 [this message]
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=49D9B21A.2000002@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