[PATCH/RFC] Linux MTD striping middle layer

[Artem B. Bityutskiy]

Alexander Belyakov wrote:
> At the stage of writing CONFIG_CMDLINE (mtdpart and mtdstripe parts) 
> user generally do not know what mtd device number will be assigned to 
> each partition. Using names IMO is a better solution if mtdstripe is a 
> built-in module since user gives and uses partition names by himself.
> 
> Using /proc/mtd and stripe mtd device by number (your suggestion) can be 
> quite good for loadable from command line mtdstripe.ko module. But using 
> two different configuration methods for built-in and loadable module can 
> be quite confusing for user.
But still, for example, if I want to use mtdram device, it is named 
"mtdram test device", and using this name as a parameter of mtdstripe.ko 
  looks insane.

> Suggested algorithm supports striping for devices with different 
> erasesize. In that (quite uncommon) case erasesize of superdevice is not 
> just erasesize of subdevice multiplied by number of subdevices.

Oh, this is interesting. You didn't mention this in the first mail, 
right? You said that flashes must be the same...

So, If I have 2 flash chips, with eraseblock size X and Y, X < Y, I 
still can stripe them? Well, fair enough. Am I right that you just merge 
eraseblocks of the second chip to make the resulting "merged" eraseblock 
not less then Y? E.g., you use N eraseblock of chip 2 for each 
eraseblock of chip 1, where N = [X/Y] + 1, right?

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