Great jffs2 speedup

[Ferenc Havasi]

Artem B. Bityutskiy wrote:

> Ferenc Havasi wrote:
>
>> It think it is the method which is really does not spoil the
>> wear-leveling. The selection of the storing place uses exactly the same
>> function what JFFS2 uses to store any other data.
>
>
> Then I just don't undesstand how it works. A user selects a bolck X
> where CS ought to be kept. JFFS2 crereates CS in X. Then, on each
> mount user specifies X in mount options. And if there are too frequent
> mounts, A becomes worn-out earlier. To avoid this, user should specify
> 2 options - where to find CS and where to store it next time? And
> evenly rotate the CS eraseblock?
>
> Or you mean JFFS2 is itself picking the needed EB? How to find it on
> next mount then?

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.

This (second) way can be usefull if there is a small root partition with
EBS and big home/usr/... with EBS+CS, and the location of the CS is
stored on the root fs. It was /a requisition of our insturial partner.

Ferenc

/