From: Helmut Raiger <helmut.raiger@hale.at>
To: linux-mtd@lists.infradead.org
Subject: Re: UBIFS: How to reserve space to be used right before power cut
Date: Wed, 26 Jun 2013 10:03:08 +0200 [thread overview]
Message-ID: <51CAA03C.4050000@hale.at> (raw)
In-Reply-To: <51BED0BE.2090701@hale.at>
On 06/17/2013 11:02 AM, Helmut Raiger wrote:
> I digged the UBI sources and still have the feeling this won't work:
>
> 1) There seems to be no way to (long term) protect a PEB from being
> moved by the wear leveling sub-system (even scrubbing on bit-flips,
> which may be induced by read-disturbances (reads on nearby pages)).
>
> 2) Temporary protection of a PEB is not really time specific, but depends
> on global PEB erase action (i.e. anything UBIFS does on the same device),
> which is something I can't control.
>
> My impression is, that UBI simply does not support this sort of
> application well. Unmoveable blocks will have a low erase count
> (below average), which is exactly what the WL should avoid.
>
> However I've never timed such a move operation:
> a) move content to a new unused PEB
> b) schedule original PEB for erasure
> It might fit into my timing requirements, but will probably be heavily
> influenced by system load and priorities.
>
> Helmut
Just an update to 'enlight the world'. We are moving to YAFFS2, it has a
deterministic garbage collector which makes it a lot easier to implement
the requested behaviour.
It seems we can even take it off the shelf, currently we are perfomance
testing the write timing.
Helmut
--
Scanned by MailScanner.
prev parent reply other threads:[~2013-06-26 8:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 11:42 UBIFS: How to reserve space to be used right before power cut Helmut Raiger
2013-06-13 11:50 ` Matthieu CASTET
2013-06-13 13:29 ` Raiger Helmut
2013-06-13 14:20 ` Matthieu CASTET
2013-06-17 9:02 ` Helmut Raiger
2013-06-26 8:03 ` Helmut Raiger [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=51CAA03C.4050000@hale.at \
--to=helmut.raiger@hale.at \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.