From: Jeremy Fitzhardinge <jeremy@goop.org>
To: (Graham Stoney) <greyham@research.canon.com.au>
Cc: linuxppc-dev@lists.linuxppc.org, linuxppc-embedded@lists.linuxppc.org
Subject: Re: linuxppc-embedded: main kernel tree
Date: Wed, 26 Jan 2000 17:53:50 -0800 (PST) [thread overview]
Message-ID: <XFMail.000126175350.jeremy@goop.org> (raw)
In-Reply-To: <20000127005854.B85911B172@elph.research.canon.com.au>
On 27-Jan-00 Graham Stoney wrote:
>
> Alan Mimms writes:
>> In fact, I'm very interested in the new cramfs I have read about as a
>> solution for our flash based file system.
>
> cramfs sure looks interesting as an alternative to an initrd uncompressed
> ramdisk or romfs.
>
> A question for the knowledgeable about memory usage efficiency of Linux's
> regular ramdisk though: does the kernel share read-only program text space
> directly with the binary image data in the ramdisk, or does it copy the data
> from the ramdisk when it execs a program?
I've done an alternative called "zbd" (compressed block/boot device). We use
it for our flash images. Its essentially the same as a ramdisk/initrd, but
each block is individually compressed. We leave the image in flash and mount
the root filesystem (ext2) from it. The implementation is almost identical to
the ramdisk code, and they could be folded together: I just haven't done that
yet.
J
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-27 1:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-26 18:31 linuxppc-embedded: main kernel tree Brendan John Simon
2000-01-26 15:55 ` Dan Malek
2000-01-26 19:00 ` Alan Mimms
2000-01-26 19:36 ` Dan Malek
2000-01-26 21:06 ` Alan Mimms
2000-01-26 21:30 ` Dan Malek
2000-01-26 21:45 ` Alan Mimms
2000-01-27 0:45 ` Graham Stoney
2000-01-26 22:36 ` Bill Roman
2000-01-27 22:09 ` Cort Dougan
2000-01-27 0:58 ` Graham Stoney
2000-01-27 1:53 ` Jeremy Fitzhardinge [this message]
2000-01-27 22:06 ` Cort Dougan
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=XFMail.000126175350.jeremy@goop.org \
--to=jeremy@goop.org \
--cc=greyham@research.canon.com.au \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).