Great jffs2 speedup

[Artem B. Bityutskiy]

> Using this (second way) when the user umounts the fs, CS stores the
> centralized summary with the same function as JFFS2 stores nodes (using
> nextblock, etc) The starting location of it can be read from sysfs after
> umount. The user has to store it somewhere else, and specify it as a
> mount option at next mount. So nothing is stored in fixed place, so I
> think it does not spoil wear-leveling.
> 

Well, are you effectively talking about the situation where there is an 
additional persistent storage available, and the CS position is kept 
there. Fair enough, providing it is available. But it is often not :-(

-- 
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.