From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Richard Purdie <richard@openedhand.com>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH RFC/testing] Upgrade the zlib_inflate library code to a recent version
Date: Tue, 4 Apr 2006 17:46:03 +0200 [thread overview]
Message-ID: <20060404154603.GF25130@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0604041737440.14611@yvahk01.tjqt.qr>
On Tue, 4 April 2006 17:38:56 +0200, Jan Engelhardt wrote:
> >
> >Upgrade the zlib_inflate implementation in the kernel from a patched
> >version 1.1.3 to a patched 1.2.3.
> >
> >The code in the kernel is about seven years old and I noticed that the
> >external zlib library's inflate performance was significantly faster
> >(~50%) than the code in the kernel on ARM (and faster again on x86_32).
> >
> Any plans to move to something newer, e.g. bzip2 or LZMA?
For PPP? Write a new RFC suggesting it and explaining how to deal
with the "chunkiness" and additional memory overhead. For JFFS2?
Bzlib compresses worse than zlib when dealing with small blocks.
For...
There may be a couple of uses where zlib could be replaced by
something else. But even ignoring the compatibility issue it isn't
always that simple.
Jörn
--
With a PC, I always felt limited by the software available. On Unix,
I am limited only by my knowledge.
-- Peter J. Schoenster
next prev parent reply other threads:[~2006-04-04 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 15:18 Richard Purdie
2006-04-04 15:33 ` Jörn Engel
2006-04-04 15:56 ` Richard Purdie
2006-04-04 16:16 ` Jörn Engel
2006-04-04 15:38 ` Jan Engelhardt
2006-04-04 15:46 ` Jörn Engel [this message]
2006-04-05 8:37 ` Jörn Engel
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=20060404154603.GF25130@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@openedhand.com \
/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®