Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 27 Sep 2006 13:51:10 -0500
From:      Eric Anderson <anderson@centtech.com>
To:        Oliver Fromme <olli@lurza.secnetix.de>
Cc:        freebsd-fs@FreeBSD.ORG
Subject:   Re: Hi: Porting Cramfs on FreeBSD
Message-ID:  <451AC81E.5070803@centtech.com>
In-Reply-To: <200609271744.k8RHipTS032655@lurza.secnetix.de>
References:  <200609271744.k8RHipTS032655@lurza.secnetix.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On 09/27/06 12:44, Oliver Fromme wrote:
> Eric Anderson wrote:
>  > I'm currently working on a tarfs, that will do something similar to 
>  > this, except it allows you to use a regular tar file as the file system 
>  > image.
> 
> That's cool.  I'm looking forward to it.
> 
>  > I don't have compression working yet, but that is on the 
>  > roadmap. [...] large file system sizes (based on available
>  > memory)
> 
> Hm.  Does that mean that the whole (uncompressed) FS image
> will have to fit into memory?  That would be a disadvantage
> compared to cramfs.  Cramfs doesn't compress the whole FS
> as one object (like .tar.gz), but it compresses it page-by-
> page, so every page can be uncompressed independently, and
> memory usage is very low, which is good for small embedded
> applications.

No, only inode+direntries need to fit into memory.  So an FS with 
1million inodes might take .5MB of memory (estimate).

Eric



-- 
------------------------------------------------------------------------
Eric Anderson        Sr. Systems Administrator        Centaur Technology
Anything that works is better than anything that doesn't.
------------------------------------------------------------------------



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?451AC81E.5070803>