From: Marc St-Jean <Marc_St-Jean@pmc-sierra.com>
To: Domen Puncer <domen.puncer@telargo.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Embedding rootfs with kernel
Date: Tue, 6 Feb 2007 08:59:53 -0800 [thread overview]
Message-ID: <45C8B408.4050203@pmc-sierra.com> (raw)
I was also looking at initramfs but from documentation I found it,
appears to expand the cpio.gz into a tmpfs (i.e. RAM) before using
it.
Since the cpio.gz is embedded into the kernel (i.e. RAM again),
won't this take twice the memory relative to embedding a
cramfs/squashfs directly in the kernel?
We only need read-only access and I believe these file systems
can be read in their compressed form without expanding and
consuming more RAM.
Marc
Domen Puncer wrote:
> On 05/02/07 12:41 -0800, Marc St-Jean wrote:
> > What is the MIPS-way of embedding the rootfs with the kernel?
>
> For 2.6.x (on all? architectures) initramfs.
>
>
> Domen
>
next reply other threads:[~2007-02-06 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 16:59 Marc St-Jean [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-06 19:03 Embedding rootfs with kernel Marc St-Jean
2007-02-05 20:41 Marc St-Jean
2007-02-06 6:49 ` Domen Puncer
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=45C8B408.4050203@pmc-sierra.com \
--to=marc_st-jean@pmc-sierra.com \
--cc=domen.puncer@telargo.com \
--cc=linux-mips@linux-mips.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