|| ||Richard Weinberger <email@example.com> |
|| ||firstname.lastname@example.org |
|| ||[RFC v2] UBI: UBIVIS (aka checkpointing) support |
|| ||Wed, 9 May 2012 19:38:38 +0200|
|| ||email@example.com, firstname.lastname@example.org, email@example.com,
|| ||Article, Thread
The following patch set implements UBIVIS (checkpointing) support for
Changes since v1:
- renamed it to UBIVIS (at least in Kconfig)
- UBIVIS parameters are now configurable via Kconfig
- several bugs have been fixed (design and implementation bugs)
- added lots of comments to make the review process easier
- made checkpatch.pl happy
Currently I'm testing UBIVIS on different workloads to find bugs
and good configuration parameters (mostly for the pool size).
So, expect v3 soon! :-)
Checkpointing is an optional feature which stores the physical to
logical eraseblock relations in a checkpointing superblock to reduce
the initialization time of UBI. The current init time of UBI is
proportional to the number of physical erase blocks on the FLASH
device. With checkpointing enabled the scan time is limited to a fixed
number of blocks.
Checkpointing does not affect any of the existing UBI robustness
features and in fact the checkpointing code falls back into scanning
mode when the checkpoint superblock(s) are corrupted.
The checkpoints consist of two elements:
1) A primary checkpoint block, which contains merily a pointer to the
erase block(s) which hold the real checkpointing data.
This primary block is guaranteed to be held within the first N
eraseblocks of a device. N is momentarily set to 64, this value can
be changed via Kconfig.
2) The secondary checkpoint blocks, which contain the real
checkpointing data (physical to logical eraseblock relations,
erase counts, sequence numbers ...)
Aside of that the checkpointing data contains a list of blocks
which belong to the active working pool. The active working pool is
a fixed number of blocks for shortterm, longterm and unknown
storage time, which can be modified before the next checkpoint set
is written to FLASH. These blocks need to be scanned in the
conventional UBI scan mode.
The reason for these pool blocks is to reduce the checkpoint
updates to the necessary minimum to avoid accelerated device
wearout in scenarios where data changes rapidly. The checkpoint
data is updated whenever a working pool runs out of blocks.
The number of pool blocks can be defined with a config option at
the moment, but this could also be done at runtime via sysfs. In
case of a change the checkpointing data would be reconstructed.
So the checkpoint scan consists of the following steps:
1) Find the primary checkpoint block by scanning the start of the
2) Read the real checkpoint data and construct the UBI device info
3) Scan the pool blocks.
All these operations scan a limited number of erase blocks which makes
the UBI init O(1) and independent of the device size.
The checkpoint functionality is fully compatible with existing UBI
deployments. If no checkpoint blocks can be found then the device is
scanned and the checkpoint blocks are created from the scanned
Aside of review and testing it needs to be decided, whether the number
of pool blocks should be deduced from the device size (number of
physical eraseblocks) or made configurable at compile or runtime.
Thanks to the folks at CELF who sponsored this work!
[PATCH 1/7] [RFC] UBI: Add checkpoint on-chip layout
[PATCH 2/7] [RFC] UBI: Add checkpoint struct to ubi_device
[PATCH 3/7] [RFC] UBI: Export next_sqnum()
[PATCH 4/7] [RFC] UBI: Export compare_lebs()
[PATCH 5/7] [RFC] UBI: Make wl subsystem checkpoint aware
[PATCH 6/7] [RFC] UBI: Implement checkpointing support
[PATCH 7/7] [RFC] UBI: wire up checkpointing
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/