mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matti Aarnio <matti.aarnio@zmailer.org>
To: John Richard Moser <nigelenki@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compressed filesystems:  Better compression?
Date: Wed, 29 Sep 2004 15:18:46 +0300	[thread overview]
Message-ID: <20040929121846.GT19844@mea-ext.zmailer.org> (raw)
In-Reply-To: <415A302E.5090402@comcast.net>

On Tue, Sep 28, 2004 at 11:46:54PM -0400, John Richard Moser wrote:
> I wonder what compression Squashfs, cramfs, and zisofs use.  I think
> cramfs uses zlib compression; I don't know of any other compression in
> the kernel tree, so I assume zisofs uses the same, as does squashfs.  Am
> I mistaken?

Compression algorithms are a bit tough to be used in a random access
smallish blocks environments.  In long streams where you can use megabytes
worth of buffer spaces there is no problem is achieving good performance.
But do try to do that in an environment where your maximum block size
is, say: 4 kB, and you have to start afresh at every block boundary.

Whatever algorithms you use, there will always be data sequences that
are of maximum entropy, and won't compress.  Rather they will be
presented in streams as is with a few bytes long wrappers around
them.

/Matti Aarnio

  parent reply	other threads:[~2004-09-29 12:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-29  3:46 John Richard Moser
2004-09-29  3:53 ` John Richard Moser
2004-09-29 16:08   ` John Richard Moser
2004-09-29 16:39   ` John Richard Moser
2004-09-29  3:55 ` John Richard Moser
2004-09-29 10:46   ` Giuseppe Bilotta
2004-09-29  8:56 ` David Woodhouse
2004-09-29 12:18 ` Matti Aarnio [this message]
2004-09-29 16:07   ` John Richard Moser
2004-09-29 12:36 ` Jörn Engel
2004-09-29 17:33   ` John Richard Moser

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=20040929121846.GT19844@mea-ext.zmailer.org \
    --to=matti.aarnio@zmailer.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigelenki@comcast.net \
    /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

all inboxes | Powered by JetHome®