From: Chris Read <chris.read@activesilicon.co.uk>
To: "Mtd (E-mail)" <linux-mtd@lists.infradead.org>
Subject: RE: Wear Leveling in JFFS2 NOT working!(?)
Date: Thu, 3 May 2001 16:51:43 +0100 [thread overview]
Message-ID: <01C0D3F1.55B02480.chris.read@activesilicon.co.uk> (raw)
There are applications where a deeply embedded system may get power cycled
frequently; thus I would advocate that wear levelling should work correctly
in this case.
Chris Read
On 03 May 2001 16:30, David Woodhouse [SMTP:dwmw2@infradead.org] wrote:
>
> vipin.malik@daniel.com said:
> > As hypothesized, the every few minutes cycling was what was screwing up
> > the wear leveling algorithm. After the cycling stopped, all sectors
> > showed up in the log and additionally each was cycled the same number
> > of times!
>
> Good :)
>
> > In my opinion, there should be no need to fix the algorithm to
> > accommodate the frequent cycling. Power going down every few minutes
> > is (usually) NOT a normal mode of operation of an embedded system.
>
> It's not normal, but given that it's quite easy for us to deal with it by
> attempting to start in a different place each time, we might as well do
so.
>
> If it were more difficult, I'd be inclined to agree with you that it's
not
> worth the effort.
>
> --
> dwmw2
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2001-05-03 15:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-03 15:51 Chris Read [this message]
2001-05-03 16:09 ` Wear Leveling in JFFS2 NOT working!(?) David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-04-30 22:26 Vipin Malik
2001-04-30 23:06 ` David Woodhouse
2001-05-01 1:24 ` Tim Riker
2001-05-01 7:21 ` David Woodhouse
2001-05-01 7:43 ` Tim Riker
2001-05-01 12:35 ` David Woodhouse
2001-05-01 11:55 ` Jim Gettys
2001-05-01 12:29 ` David Woodhouse
2001-05-03 15:27 ` Vipin Malik
2001-05-03 15:29 ` David Woodhouse
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=01C0D3F1.55B02480.chris.read@activesilicon.co.uk \
--to=chris.read@activesilicon.co.uk \
--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