lkml.org 
[lkml]   [2001]   [Jan]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] cramfs is ro only, so honour this in inode->mode


On Tue, 9 Jan 2001, Rusty Russell wrote:
> In message <Pine.LNX.4.10.10101080930410.3750-100000@penguin.transmeta.com> you
> write:
> > I've been thinking of doing a cramfs2, and the only thing I'd change is
> > (a) slightly bigger blocksize (maybe 8k or 16k) and (b) re-order the
> > meta-data and the real data so that I could easily compress the metadata
> > too. cramfs doesn't have any traditional meta-data (no bitmap blocks or
> > anything like that), but it wouldn't be that hard to put the directory
> > structure in the page cache and just compress the directories the same way
> > the real data is compressed.
>
> And you'd still be worse than compressed loopback w/32k blocks, and
> more complex. Now most of the loopback bugs seem fixed in 2.4, I'll
> port the cloop stuff, and we can compare.

If you compare, make sure that you don't compare the way some people seem
to compare. They see how well the ext2 image compresses, and ignore the
fact that the ext2 image itself has a lot of extraneous stuff (alignment,
bitmaps, very compressible meta-data etc).

The only valid comparison is how big the actual image file is for the same
trees. Also, you should take into account the size of the ext2 module and
cloop. I don't think you'd win.

Linus

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:52    [W:0.045 / U:1.476 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site