On Tue, 2012-08-07 at 09:29 +0200, Richard Weinberger wrote:> Am 07.08.2012 06:21, schrieb Artem Bityutskiy:> > On Mon, 2012-08-06 at 19:36 +0200, Richard Weinberger wrote:> >> I think we enable fastmap only if a MTD device has more than> >> UBI_FM_MAX_START*2 PEBs.> >> Any comments?> > > > With double space one can make it power-cut tolerant, because you should> > be able to have either old or new fastmap at any point of time.> > UBI_FM_MAX_START*2 has nothing do to with the Fastmap size.> IMHO we need a threshold where Fastmap makes sense.> Technically Fastmap can only be used if a MTD device has >= UBI_FM_MAX_START> PEBs.> But does this makes sense? Fastmap was invented to speedup attaching on *large* MTDs,> The benefit in small MTDs is very little.

You may measure when it starts being reasonable to have fastmap enabled,or interpolate the data you already have (everything is roughly linear,should be rather easy).

But of course small flashes do not need fastmap.

Also, did you say in the past that you are going to come up with adocument describing the design, its cons and pros, limitations, and somenumbers. It would help a lot. Even a limited document would be betterthan none.

Speaking about numbers, how long does it take to re-write fastmap on agiven flash (say, 1GiB or larger, depending on what HW you have)? Howbig is fastmap for a given partitions size? I'd really prefer to seethis information in a document, e.g., a text file, rather than spreadover many e-mails.