From: David Woodhouse <dwmw2@infradead.org>
To: "Xiaogeng (Shawn) Jin" <xjin@redswitch.com>
Cc: "Jörn Engel" <joern@wohnheim.fh-wedel.de>,
"Kenneth Johansson" <kenneth.johansson@etx.ericsson.se>,
Mtd <linux-mtd@lists.infradead.org>
Subject: Re: writing to jffs2 is so slow?
Date: Fri, 06 Sep 2002 19:54:15 +0100 [thread overview]
Message-ID: <29521.1031338455@redhat.com> (raw)
In-Reply-To: <3D78F4A1.4060304@redswitch.com>
xjin@redswitch.com said:
> > Try eraseall from the utils.
> > With that, jffs2 just writes the erase markers to flash, 12 bytes per
> > erase block.
No, JFFS2 cannot trust that 'empty' blocks really have been properly
erased, and must erase them again, writing a 'cleanmarker' node to them
when the erase is complete.
> Well, that's just what I did. Then making a first directory takes 2
> minutes.
JFFS2 is busy erasing every block on the file system. You have to wait
until it's done before you can write.
Hacking the 'eraseall' program so it writes a 'cleanmarker' node to the
beginning of every block erased is left as an exercise for the reader.
Other possibilities include a mount time option to tell JFFS2 that it
should trust the flash and not re-erase the blocks, and/or changing the
jffs2_write_super()/jffs2_erase_pending_blocks() to only erase a few blocks
at a time, so you only have to wait for a few blocks to be erased, not the
whole flash.
--
dwmw2
next prev parent reply other threads:[~2002-09-06 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-05 21:09 writing to jffs2 is so slow? Xiaogeng (Shawn) Jin
2002-09-06 7:15 ` Thomas TESTASECCA
2002-09-06 12:08 ` Kenneth Johansson
2002-09-06 17:14 ` Xiaogeng (Shawn) Jin
2002-09-06 17:48 ` Jörn Engel
2002-09-06 18:32 ` Xiaogeng (Shawn) Jin
2002-09-06 18:54 ` David Woodhouse [this message]
2002-09-06 21:20 ` Joakim Tjernlund
2002-09-06 21:30 ` David Woodhouse
2002-09-06 18:57 ` Jörn Engel
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=29521.1031338455@redhat.com \
--to=dwmw2@infradead.org \
--cc=joern@wohnheim.fh-wedel.de \
--cc=kenneth.johansson@etx.ericsson.se \
--cc=linux-mtd@lists.infradead.org \
--cc=xjin@redswitch.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