From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: David Lang <david.lang@digitalinsight.com>
Cc: Jeff Garzik <jgarzik@pobox.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 22:05:54 +0200 [thread overview]
Message-ID: <20030620200554.GC22732@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0306201247560.28021-100000@dlang.diginsite.com>
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.
Which is why kernel images usually come as .bz2 today. ;)
Read my first posting, read the source (grep for BZMALLOC, there are
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.
This might boil down to bzlib merge 100% (minus testing and sending
patches) done and <nifty_name>, which is based on bzlib, just started.
Comments?
Jörn
--
Beware of bugs in the above code; I have only proved it correct, but
not tried it.
-- Donald Knuth
next prev parent reply other threads:[~2003-06-20 19:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-20 18:59 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 [this message]
2003-06-20 21:53 ` Jeff Garzik
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=20030620200554.GC22732@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=davem@redhat.com \
--cc=david.lang@digitalinsight.com \
--cc=dwmw2@infradead.org \
--cc=jgarzik@pobox.com \
--cc=jmorris@intercode.com.au \
--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
all inboxes | Powered by JetHome®