From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Tim Yamin <plasmaroo@gentoo.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH UPDATE] deflate stack usage in lib/inflate.c
Date: Thu, 12 Apr 2007 16:31:04 -0700 [thread overview]
Message-ID: <461EC138.10407@goop.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0704130119470.14441@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
> On Apr 12 2007 15:39, Jeremy Fitzhardinge wrote:
>
>> Andi Kleen wrote:
>>
>>> Hmm, does Xen perhaps not use interrupt stacks? Normally 2.7k should be still
>>> green as long as there are not too many functions above/below it.
>>>
>> That's a good point, I'll need to check that. Still, nearly 3k of stack!
>>
>
> I bite. Would compressing the vmlinux binary with LZO or LZMA make an
> improvement to the bootstrap uncompress stack usage?
>
Well, the thread started with my patch to fix inflate. The stack usage
of LZO or LZMA decompressors will primarily depend on how they're
implemented rather than any inherent property of the algorithms.
J
next prev parent reply other threads:[~2007-04-12 23:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 8:25 [PATCH] deflate stack usage in lib/inflate.c Jeremy Fitzhardinge
2007-04-12 20:50 ` [PATCH UPDATE] " Jeremy Fitzhardinge
2007-04-12 21:21 ` Andi Kleen
2007-04-12 22:39 ` Jeremy Fitzhardinge
2007-04-12 23:20 ` Jan Engelhardt
2007-04-12 23:31 ` Jeremy Fitzhardinge [this message]
2007-04-12 23:37 ` Andi Kleen
2007-04-12 22:56 ` Jeremy Fitzhardinge
2007-04-12 23:02 ` Andi Kleen
2007-04-13 0:00 ` Jeremy Fitzhardinge
2007-04-12 23:06 ` Chuck Ebbert
2007-04-12 22:25 ` Matt Mackall
2007-04-12 22:57 ` Jeremy Fitzhardinge
2007-04-12 22:53 ` Matt Mackall
2007-04-16 21:04 ` Russell King
2007-04-13 18:42 ` 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=461EC138.10407@goop.org \
--to=jeremy@goop.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=plasmaroo@gentoo.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