mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Pavel Machek <pavel@suse.cz>
Cc: Matt Mackall <mpm@selenic.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	discuss@x86-64.org, Tom Rini <trini@kernel.crashing.org>
Subject: Re: [discuss] Re: [CFT] inflate.c rework arch testing needed
Date: Thu, 1 Apr 2004 14:14:17 +0200	[thread overview]
Message-ID: <20040401121417.GA8185@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20040328070015.GB1453@openzaurus.ucw.cz>

On Sun, 28 March 2004 09:00:15 +0200, Pavel Machek wrote:
> 
> > The code for new versions of zlib is significantly scarier last I
> > checked and there's no particular advantage to it. But one of the
> > primary motivations here is to get to the point where something like
> > bunzip2 or even a new zlib is a drop-in replacement.
> 
> Some people want fast-but-not-big-ratio compressor for speeding up swsusp.
> If compressors are drop-in, thats very good.

Also keep in mind, which zlib you are talking about.  Matt's patch is
to lib/inflate.c, which is used exclusively for the bootloader which
is built-in to the kernel on some arches.  That one was always far
behind and scary to look at.

The real kernel zlib is in a somewhat better state, many people cared
about and worked on it.  It's not great either, but at least better.
And yes, drop-in replacement or even runtime choice would be nice here.

Jörn

-- 
The story so far:
In the beginning the Universe was created.  This has made a lot
of people very angry and been widely regarded as a bad move.
-- Douglas Adams?

  reply	other threads:[~2004-04-01 12:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-18 23:10 Matt Mackall
2004-03-19  0:32 ` Jörn Engel
2004-03-19  3:09   ` Matt Mackall
2004-03-19  9:29     ` Jörn Engel
2004-03-28  7:00     ` [discuss] " Pavel Machek
2004-04-01 12:14       ` Jörn Engel [this message]
2004-03-19 10:31 ` Russell King
2004-03-19 17:16   ` Matt Mackall
2004-03-19 21:39     ` Russell King
2004-03-19 22:25       ` Matt Mackall

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=20040401121417.GA8185@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=pavel@suse.cz \
    --cc=trini@kernel.crashing.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®