mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Josh Boyer" <jwboyer@gmail.com>
To: "Jared Hulbert" <jaredeh@gmail.com>
Cc: "Jan Engelhardt" <jengelh@linux01.gwdg.de>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Advanced XIP File System
Date: Wed, 3 May 2006 18:17:50 -0500	[thread overview]
Message-ID: <625fc13d0605031617v44c2b278kbf12e00781f55ae6@mail.gmail.com> (raw)
In-Reply-To: <6934efce0605031154l225caee8yc217c6e63c0dd441@mail.gmail.com>

On 5/3/06, Jared Hulbert <jaredeh@gmail.com> 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.

josh

  reply	other threads:[~2006-05-03 23:17 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-02 21:53 Jared Hulbert
2006-05-03  0:00 ` Arnd Bergmann
2006-05-03  1:59   ` Jared Hulbert
2006-05-03  2:27     ` Josh Boyer
2006-05-03  5:04       ` Jared Hulbert
2006-05-03  8:31         ` David Woodhouse
2006-05-03 19:14     ` Pavel Machek
2006-05-04 16:32       ` Jared Hulbert
2006-05-03  0:56 ` Josh Boyer
2006-05-03  3:17   ` Nicolas Pitre
2006-05-03 10:41     ` Josh Boyer
2006-05-03 12:11       ` David Woodhouse
2006-05-03 15:45         ` Jared Hulbert
2006-05-03 15:52           ` David Woodhouse
2006-05-03 15:57           ` Nicolas Pitre
2006-05-03 16:01             ` David Woodhouse
2006-05-03 16:10               ` Nicolas Pitre
2006-05-03  5:11   ` Jared Hulbert
2006-05-03 12:50 ` Mark Lord
2006-05-03 15:33   ` Jared Hulbert
2006-05-03 13:05 ` Jörn Engel
2006-05-03 15:31   ` Jared Hulbert
2006-05-03 15:47     ` Jörn Engel
2006-05-03 15:58       ` Jared Hulbert
2006-05-03 17:03         ` Jörn Engel
2006-05-03 18:58           ` Jared Hulbert
2006-05-03 16:38 ` Jan Engelhardt
2006-05-03 18:54   ` Jared Hulbert
2006-05-03 23:17     ` Josh Boyer [this message]
2006-05-03 23:48       ` Jared Hulbert
2006-05-04  0:21         ` Josh Boyer
2006-05-03 22:49   ` David Woodhouse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=625fc13d0605031617v44c2b278kbf12e00781f55ae6@mail.gmail.com \
    --to=jwboyer@gmail.com \
    --cc=jaredeh@gmail.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®