From: "H. Peter Anvin" <hpa@zytor.com>
To: Coywolf Qi Hunt <coywolf@gmail.com>
Cc: Axel Kittenberger <axel.kernel@kittenberger.net>,
linux-kernel@vger.kernel.org
Subject: Re: Possible Bootloader Optimization in inflate (get rid of unnecessary 32k Window)
Date: Mon, 26 Dec 2005 08:00:16 -0800 [thread overview]
Message-ID: <43B01390.6010206@zytor.com> (raw)
In-Reply-To: <2cd57c900512251815r16422013p@mail.gmail.com>
Coywolf Qi Hunt wrote:
>>
>>What would the optimization be worth?
>>* A faster uncompressing of the kernel, since a total 1-time memcopy of the
>>whole kernel is been optimized away.
>>* I'm not sure about the size, the memory or disk footprint. If the 32k static
>>(!) memory array in compressed/misc.c, I don't know if it safes 32k running
>>memory, or 32k on-disk size. Since I don't know the indepth working of these
>
> Neither for saving running memory (discarded), nor on-disk size
> (window[WSIZE] resides in BSS).
>
I've actually implemented this for another application (where BSS was at
a premium.) It even has some nice benefits for code size if you do it
right.
It indeed would avoid a cache-to-memory copy, but that's not really a
huge deal, which is why noone has worried too much about it.
-hpa
prev parent reply other threads:[~2005-12-26 16:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 12:52 Possible Bootloader Optimization in inflate (get rid of unnecessary 32k Window) Axel Kittenberger
2005-12-22 17:37 ` Marc Singer
2005-12-22 18:12 ` Axel Kittenberger
2005-12-22 18:30 ` Marc Singer
2005-12-22 19:04 ` Axel Kittenberger
2005-12-23 8:53 ` Hans Kristian Rosbach
2005-12-24 21:38 ` Jan Engelhardt
2005-12-25 21:01 ` Folkert van Heusden
2005-12-25 21:10 ` Axel Kittenberger
2005-12-25 21:17 ` Jan Engelhardt
2005-12-26 2:15 ` Coywolf Qi Hunt
2005-12-26 16:00 ` H. Peter Anvin [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=43B01390.6010206@zytor.com \
--to=hpa@zytor.com \
--cc=axel.kernel@kittenberger.net \
--cc=coywolf@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.