[PATCH] remove support for virtual blocks

Jörn Engel joern at wohnheim.fh-wedel.de
Tue Aug 30 05:56:10 EDT 2005


On Mon, 29 August 2005 16:21:51 -0700, Jared Hulbert wrote:
> > 
> I need support for 256KiB eraseblocks. There are high volume consumer 
> devices hitting the market now which use that eraseblock size. More will be 
> coming. 512KiB is feasible in the near future.
> 
> I'm not sure I fully understand the issues involved. 
> 
> Is there something magical about the (128*1024)? Can we increase that to 256 
> or 512?

You cannot kmalloc() more than 128k in a chunk.  Depending on your
system, you could vmalloc() more.

It's not the eraseblock size that matters, it's the number of erase
blocks.  One struct jffs2_eraseblock is needed for each and right now,
they are put into a large array, allocated by kmalloc().  This array
hits the ceiling at 128k.

What we have to do is allocate the memory in smaller chunks and put
some effort into organizing it.  A slab cache would be the best idea.

Jörn

-- 
He who knows others is wise.
He who knows himself is enlightened.
-- Lao Tsu




More information about the linux-mtd mailing list