From: Jeff Garzik <jgarzik@pobox.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: David Lang <david.lang@digitalinsight.com>,
linux-kernel@vger.kernel.org, jmorris@intercode.com.au,
davem@redhat.com, David Woodhouse <dwmw2@infradead.org>
Subject: Re: [RFC] Breaking data compatibility with userspace bzlib
Date: Fri, 20 Jun 2003 17:53:12 -0400 [thread overview]
Message-ID: <3EF38248.2070807@pobox.com> (raw)
In-Reply-To: <20030620200554.GC22732@wohnheim.fh-wedel.de>
Jörn Engel wrote:
> On Fri, 20 June 2003 12:48:51 -0700, David Lang wrote:
>>he is saying that the memory and CPU requirements to do the bzip
>>uncompression are so much larger then what is nessasary to do the gzip
>>uncompression that the small amount of space saved is almost never worth
>>the cost.
exactly
> just a few). It is impossible in it's current state to use less than
> roughly 1MB of memory, even though the algorithm doesn't give that
> restriction at all. Drop that down to 280k, the current zlib value
> and you won't see a difference in compression ratios for jffs2 at
> least.
Well, if you drop that down to 280k, and you do not beat zlib
compression by a "comfortable margin", it's just pointless code churn in
addition to swapping out the faster algorithm for the slower algorithm.
If you drop that down to 280k with much better compression than zlib,
that's fantastic and useful, and people won't mind the slower algorithm :)
The issue of memory usage at high compression rates was the main reason
why I didn't push the patch upstream and pursue bzlib further.
Jeff
next prev parent reply other threads:[~2003-06-20 21:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-20 18:59 [RFC] Breaking data compatibility with userspace bzlib Jörn Engel
2003-06-20 19:09 ` Jeff Garzik
2003-06-20 19:45 ` Jörn Engel
2003-06-20 19:48 ` David Lang
2003-06-20 20:05 ` Jörn Engel
2003-06-20 21:53 ` Jeff Garzik [this message]
2003-06-20 21:55 ` Jeff Garzik
2003-06-20 20:27 ` [RFC] Breaking data compatibility with userspace bz2lib Nicholas Wourms
2003-06-20 20:51 ` Jörn Engel
2003-06-20 21:34 ` Jeff Garzik
2003-06-20 19:45 ` [RFC] Breaking data compatibility with userspace bzlib David S. Miller
2003-06-20 19:56 ` Jörn Engel
2003-06-20 20:23 ` David S. Miller
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=3EF38248.2070807@pobox.com \
--to=jgarzik@pobox.com \
--cc=davem@redhat.com \
--cc=david.lang@digitalinsight.com \
--cc=dwmw2@infradead.org \
--cc=jmorris@intercode.com.au \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.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