[lkml]   [2006]   [May]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC] Advanced XIP File System
On 5/3/06, Jared Hulbert <> wrote:
> We took Familiar Linux 0.8.3 Opie verision and built two versions, one
> that used jffs2 on NAND and another that used XIP cramfs on NOR. We

Erm, why was one built on NAND and one on NOR? You're comparing
apples to oranges now.

You're also comparing different price points. Depending on various
factors, NAND flash can be 3x cheaper than NOR. But I agree that
economics should be left out of this discussion. There are people
that want to use XIP, and economics has nothing to do with the
technology that enables that to happen.

> optimized the XIP cramfs to only uncompress commonly used libraries
> and binaries. The XIP build used 8MiB more flash. It saved about
> 20MiB of RAM and was 3X faster at bootup. (Summary support on jffs2
> closed the gap to 2X boot up but made the jffs2 use _more_ flash than
> the XIP). The jffs2 version volume wouldn't run the PIM apps and the

If the NAND device was a small block device, summary support won't
really help at all there.

> browser and Quake at the same time with only 32MiB of RAM. The XIP
> version would. The jffs2 version used 42MiB and the XIP 50MiB.
> Rounding to rational chip sizes that's 32MiB RAM/64MiB Flash versus
> 64MiB RAM/64MiB Flash.

JFFS2 does incur a bit of DRAM overhead. There are a couple things
kicking around that might help that consumption, but not in the
magnitude you're mentioning here.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-05-04 01:20    [W:0.038 / U:3.540 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site