From: "zhao, forrest" <forrest.zhao@intel.com>
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: Fri, 18 Nov 2005 17:11:28 +0800 [thread overview]
Message-ID: <1132305088.18546.8.camel@localhost.localdomain> (raw)
In-Reply-To: <200511171227.20593.david.jander@protonic.nl>
On Thu, 2005-11-17 at 13:27 +0200, David Jander wrote:
> Hi,
>
> 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. Only thing is, although the experiment has lasted
> quite long already (in terms of amount of data (re-)written), it doesn't seem
> anyway near as long as expected, when making some "educated guesses" about
> the perfomrance of jffs2.
This is really good! By my patch for erase count tracking in
JFFS2, you may read the erase count of each erase block using jffs2dump.
My patch for enhanced WL is also in MTD CVS now. You may also test how
good this new WL is :)
For testing, I think using RAM test driver is enough when we can know
the erase count of each erase block.
Thanks,
Forrest
prev parent reply other threads:[~2005-11-18 9:16 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
2005-11-18 9:11 ` zhao, forrest [this message]
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=1132305088.18546.8.camel@localhost.localdomain \
--to=forrest.zhao@intel.com \
--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