From: Marc Singer <elf@buici.com>
To: Russ Dill <Russ.Dill@asu.edu>
Cc: Charles Manning <manningc2@actrix.gen.nz>,
linux-mtd@lists.infradead.org, yaffs@toby-churchill.org
Subject: Re: Interest in DOC and YAFFS? --> YAFFS bootloading
Date: Tue, 24 Sep 2002 11:33:14 -0700 [thread overview]
Message-ID: <20020924183314.GA3074@buici.com> (raw)
In-Reply-To: <1032888645.13282.11.camel@russ>
On Tue, Sep 24, 2002 at 10:30:45AM -0700, Russ Dill wrote:
> > > > A question, though. I've been doing compression tests with cramfs.
> > > > I'm finding that gzip -9 of an ext2 filesystem produces smaller images
> > > > than mkcramfs. Have you ever compared the two?
> > >
> > > cramfs is meant to be lean, fast, and low on ram consumption, if you
> > > compress the whole thing at once, you have to load the whole thing into
> > > ram to read any of it, so cramfs compresses PAGE_CACHE (4096) sized
> > > pages at a time
> >
> > That's what isn't clear. I made two filesystems with the same
> > contents. One cramfs and the other ext2. The ext2 filesystem
> > compressed was smaller than the cramfs. My understanding is that both
> > must be uncompressed into a ramfs to be used. If this is correct,
> > then the only comparable consideration is the size of the compressed
> > data.
>
> no, a cramfs does not need to be loaded into a ramfs, only the pages
> that are needed are loaded from the cramfs, and if memory is in a pinch,
> fs pages can be dropped. If you gzip a 4M file at once, vs gzip 4096
> byte pieces of it at a time, the former will end up smaller. (deflate
> uses repetition of information, and runs of things).
>
> of course, it depends which you want, greatly optimized memory usage
> (cramfs), or a slightly smaller image.
Yes, that is the trade off. I was unclear about how cramfs was
loaded. It was my understanding that the cramfs was unpacked into a
ramfs so that the fs could be used R/W.
I'll evaluate it again when I have a chance.
next prev parent reply other threads:[~2002-09-24 18:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 9:20 jffs2 and Doc 2000 eylon eyal
2002-09-24 0:03 ` Interest in DOC and YAFFS? Charles Manning
2002-09-24 3:44 ` Marc Singer
2002-09-24 3:58 ` Interest in DOC and YAFFS? --> YAFFS bootloading Charles Manning
2002-09-24 4:44 ` Marc Singer
2002-09-24 7:53 ` Russ Dill
2002-09-24 16:53 ` Marc Singer
2002-09-24 16:59 ` Russ Dill
2002-09-24 17:14 ` Marc Singer
2002-09-24 17:21 ` Brian J. Fox
2002-09-24 17:30 ` Russ Dill
2002-09-24 18:33 ` Marc Singer [this message]
2002-09-24 17:44 ` Kenneth Johansson
2002-09-24 18:37 ` Marc Singer
2002-09-24 18:47 ` Russ Dill
2002-09-24 20:22 ` Marc Singer
2002-09-24 20:41 ` Russ Dill
2002-09-24 7:23 ` Nick Bane
2002-09-24 16:55 ` Marc Singer
2002-09-24 18:23 ` Nick Bane
2002-09-24 20:53 ` Interest in DOC and YAFFS? Charles Manning
2002-09-24 22:46 ` Christian Gan
2002-09-25 7:33 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2002-09-25 7:09 Interest in DOC and YAFFS? --> YAFFS bootloading Srinivasan.Ramasubramaniam
2002-09-25 8:38 ` Russ Dill
2002-09-25 13:34 ` Henrik Nordström
2002-09-25 16:34 ` Russ Dill
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=20020924183314.GA3074@buici.com \
--to=elf@buici.com \
--cc=Russ.Dill@asu.edu \
--cc=linux-mtd@lists.infradead.org \
--cc=manningc2@actrix.gen.nz \
--cc=yaffs@toby-churchill.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