From: Tom Rini <trini@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH,RFC 2.6.9-rc1 2/2] zlib_inflate: Add __BOOTER__ around zlib_inflate_trees_fixed(...)
Date: Fri, 3 Sep 2004 10:40:10 -0700 [thread overview]
Message-ID: <20040903174010.GB6290@smtp.west.cox.net> (raw)
In-Reply-To: <20040903014520.GE26144@smtp.west.cox.net>
On Thu, Sep 02, 2004 at 06:45:20PM -0700, Tom Rini wrote:
> On Fri, Sep 03, 2004 at 11:14:34AM +1000, Paul Mackerras wrote:
>
> > Tom Rini writes:
> >
> > > This is the second part of what I found. zlib_inflate_trees_fixed(...)
> > > isn't called in decompressing a kernel. Dropping this, and the call to
> >
> > I think it is just luck that gzip hasn't used the fixed table in
> > compressing the kernel. I don't think we have any guarantee that gzip
> > won't use the fixed table.
>
> That is a good point. Looking at arch/ppc/boot/lib/zlib.c it generates
> the table, instead of having a static one. So perhaps we should move to
> that instead for lib/zlib_inflate ?
I've moved lib/zlib_inflate over to generating the table. But, in
trying to test it, I haven't been able to find anything that will
actually use this (it appears that using this static table was something
that pkzip introduced long ago as an alternative method of good
compression / speed) so I can't actually test it. But the image size is
back in line.
--
Tom Rini
http://gate.crashing.org/~trini/
prev parent reply other threads:[~2004-09-03 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 23:17 [PATCH 2.6.9-rc1] ppc32: Switch arch/ppc/boot to zlib_inflate Tom Rini
2004-09-02 17:36 ` [PATCH,RFC 2.6.9-rc1 1/2] zlib_inflate: Move zlib_inflateSync & friends Tom Rini
2004-09-02 17:47 ` [PATCH,RFC 2.6.9-rc1 2/2] zlib_inflate: Add __BOOTER__ around zlib_inflate_trees_fixed(...) Tom Rini
2004-09-03 1:14 ` Paul Mackerras
2004-09-03 1:45 ` Tom Rini
2004-09-03 17:40 ` Tom Rini [this message]
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=20040903174010.GB6290@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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®