squashfs on ppc

2005-09-22 Thread Tolunay Orkun
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).
>
>  
>




squashfs on ppc

2005-09-16 Thread Tolunay Orkun
Hi,

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?

Best regards,
Tolunay



squashfs on ppc

2005-09-16 Thread Eugene Surovegin
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).

-- 
Eugene