linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tolunay Orkun <listmember@orkun.us>
To: Eugene Surovegin <ebs@ebshome.net>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: squashfs on ppc
Date: Thu, 22 Sep 2005 15:10:01 -0500	[thread overview]
Message-ID: <43330F99.3010906@orkun.us> (raw)
In-Reply-To: <20050916224131.GA9941@gate.ebshome.net>

Thanks for the reply. I've built file system images based on ext2, 
cramfs and squashfs (2.1).

Uncompressed ext2 image is about 12MB consisting mostly of busybox, 
other executables and shared libraries etc. Everything is stripped.

cramfs based image took the least ram allocation but the most flash 
space (18% more than gzipped ext2 image).
squashfs was close to cramfs in ram usage but was about equal to gzipped 
ext2 image.

Thus, I have found squashfs based initrd to be good blance between ram 
and flash.


Eugene Surovegin wrote:

>On Fri, Sep 16, 2005 at 04:48:09PM -0500, Tolunay Orkun wrote:
>  
>
>>Has anyone any positive or negative experience of using squashfs on 
>>PowerPC as initrd?
>>
>>Our environment is PowerPC 405GP running 2.4.31 kernel. U-Boot is our 
>>bootloader. Any comparison with respect to CramFS?
>>    
>>
>
>I use squashfs and squashfs2. Both work just fine on PPC.
>
>They provide significantly better compression ration than cramfs, 
>although at the expense of some speed (mostly visible during initial 
>startup of big user-space app).
>
>  
>

      reply	other threads:[~2005-09-22 20:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-16 21:48 squashfs on ppc Tolunay Orkun
2005-09-16 22:41 ` Eugene Surovegin
2005-09-22 20:10   ` Tolunay Orkun [this message]

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=43330F99.3010906@orkun.us \
    --to=listmember@orkun.us \
    --cc=ebs@ebshome.net \
    --cc=linuxppc-embedded@ozlabs.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).