From: Jarkko Lavinen <jlavi@iki.fi>
To: linux-mtd@lists.infradead.org
Subject: Slow mtd device & JFFS2
Date: Wed, 15 Aug 2001 21:22:40 +0300 [thread overview]
Message-ID: <20010815212240.A22207@kosh.hut.fi> (raw)
I am playing with embedded device with Arm925 @ 13MHz. JFFS2 works,
but it is painfully slow. I have made some measurements and it
looks like the reason must be very slow write access to flash chip.
eraseall /dev/mtd0: 258 s (= 2.0 s/sector)
copying (dd) /dev/mtd0 to /dev/null: 35 s (= 240 kiB/s or 8 us/word)
copying (dd) /dev/zero to /dev/mtd0: 899 s (= 9.3 kiB/s or 210 us/word
Mounting an empty 8 MiB filesystem: 40 s
Copying ~ 300 kiB files to JFFS2 ~ 5 min
Mounting ~700 kiB filesystem: 70 s
These figures are with compression off: jffs2_compress() is here
patched to return always JFFS2_COMPR_NONE. JFFS2 debugging level is
0. MTD debugging level is 0. CPU gives 11.1 BogoMIPS. I am using
couple days old mtd CVS image but my kernel version is rather old,
2.4.2. The 8MiB flash chip shows in physical memory as continous
area and I am using mapping similar to physmap.c.
The writing speed looks awful! The chip is AMD 64Mbit chip for which
AMD claims 11 us typical programming time per word and 360 us worst
case. Read and erase figures look normal.
Is the slow write access the main reason for painfully slow JFFS2?
Jarkko Lavinen
reply other threads:[~2001-08-15 18:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010815212240.A22207@kosh.hut.fi \
--to=jlavi@iki.fi \
--cc=linux-mtd@lists.infradead.org \
/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