UBI partitioning in embedded device?

[Artem Bityutskiy]

On Mon, 2011-04-18 at 14:53 +0200, Ricard Wanderlof wrote:
> On Mon, 18 Apr 2011, Atlant Schmidt wrote:
> 
> > Ricard:
> >
> > One advantage of moving critical data (such as calibration
> > data) into its own partition is that because each partition
> > would absolutely positively *NOT* share its PEBs (Physical
> > Erase Blocks) with any other partition, data stored in
> > those partitions would then be better-insulated from
> > "disturb" effects (such as "program disturb" and "read
> > disturb") caused by the reading and writing of other data.
> >
> > Generally, the "disturb" effects only take place within Flash pages and 
> > from one Flash page to another.
> 
> But is it even possible to have an UBI volume less than one eraseblock in 
> size? Normally a UBI volume would be several eraseblocks, so there's no 
> chance of any eraseblocks being shared at any one time between different 
> UBI volumes.
> 
> I've always thought that because UBI volumes are measured in 
> number-of-LEBs, that each volume in practice gets its own PEBs, even 
> though of course UBI can move them around in the flash if it wants to.

That's right, minimum size is one LEB. Probably Atlant meant that UBI
will move data around, so the same PEBs will be "shared", meaning that
today your critical calibration data is in PEB 1, tomorrow PEB 1
contains some random non-critical stuff.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)