From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: David Jander <david.jander@protonic.nl>
Cc: MTD mailing list <linux-mtd@lists.infradead.org>
Subject: Re: Performance of wear-levelling in JFFS2.
Date: Thu, 17 Nov 2005 14:13:57 +0100 [thread overview]
Message-ID: <20051117131357.GA26258@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <200511171227.20593.david.jander@protonic.nl>
On Thu, 17 November 2005 13:27:20 +0200, David Jander wrote:
>
> I am wondering about how good wear-levelling really is in JFFS2. I have made
> an experiment which ended with a "MTD do_write_buffer(): software timeout",
> which really looks like flash is taking too long to write data because of it
> beeing near end of life.
Nice experiment, although "really looks like" is not exactly a
comparable result. How about changing one of the ram test drivers to
count the number of erases per block, let the experiment run for a
while and then print those number?
Jörn
--
Mac is for working,
Linux is for Networking,
Windows is for Solitaire!
-- stolen from dc
next prev parent reply other threads:[~2005-11-17 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 11:27 Performance of wear-levelling in JFFS2 David Jander
2005-11-17 13:13 ` Jörn Engel [this message]
2005-11-18 9:11 ` zhao, forrest
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=20051117131357.GA26258@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=david.jander@protonic.nl \
--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