| |||
What is the goal of this subproject?The main goal is to speed up the mount time of JFFS2 - specially when it uses NAND flash. Our technique is called summary. There are two kinds of summary:
How does Erase Block Summary work?EBS stores summary information at the end of every (closed) erase block. It is no longer necessary to scan all nodes separetly (and read all pages of them) just read this "small" summary, where every information is stored which is need at mounttime. This summary information is stored in a JFFS2_FEATURE_RWCOMPAT_DELETE. During the mount process if there is no summary info the orignal scan process will be executed. There is a user space tool called sumtool to generate this summary information for a JFFS2 image. EBS works with NAND and NOR flashes, too. It is now part of the official JFFS2. How does Centralized Summary work?CS stores every important memory data structures (relevant parts of inode cache, raw node references, jeb info and lists) onto the flash at umount time. If there was clean umount at the next mount this stored information will be read directly into the memory and additional scanning will not be neccesarry. There is no user space tool for CS. The first mount will use the original scanning process, and from the second mount will be fast (if there was clean umount before). CS can store summary information in two ways (can be selected by kconfig):
CS is a very new technique, it should be tested. Now it works only on NAND flashes. Downloads
Usage of summary
|