From: Chris Wedgwood <cw@f00f.org>
To: Andrew Morton <akpm@digeo.com>
Cc: Daniel Egger <degger@fhm.edu>, linux-kernel@vger.kernel.org
Subject: Re: Kernel bloat 2.4 vs. 2.5
Date: Tue, 4 Mar 2003 17:59:57 -0800 [thread overview]
Message-ID: <20030305015957.GA27985@f00f.org> (raw)
In-Reply-To: <20030304154105.7a2db7fa.akpm@digeo.com>
On Tue, Mar 04, 2003 at 03:41:05PM -0800, Andrew Morton wrote:
> Daniel Egger <degger@fhm.edu> wrote:
> > I've seen surprisingly few messages about the dramatic size
> > increase between a simple 2.4 and a 2.5 kernel image.
> 2.4 has magical size reduction tricks in it which were not brought
> into 2.5 because we expect that gcc will do it for us.
I can't see it helping *that* much, for me I have:
charon:~/wk/linux% size 2.4.x-cw/vmlinux bk-2.5.x/vmlinux
text data bss dec hex filename
2003887 120260 191657 2315804 23561c 2.4.x-cw/vmlinux
2411323 267551 181004 2859878 2ba366 bk-2.5.x/vmlinux
gcc version 2.95.4 20011002 (Debian prerelease)
this is for functionally (in terms of .config) equivalent kernels.
--cw
next prev parent reply other threads:[~2003-03-05 1:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 22:42 Kernel bloat 2.4 vs. 2.5 Daniel Egger
2003-03-04 23:41 ` Andrew Morton
2003-03-05 1:59 ` Chris Wedgwood [this message]
2003-03-05 2:11 ` Andrew Morton
2003-03-05 2:23 ` Robert Love
2003-03-05 2:32 ` Andrew Morton
2003-03-05 2:37 ` Robert Love
2003-03-05 3:13 ` Steven Cole
2003-03-05 3:06 ` Chris Wedgwood
2003-03-05 2:35 ` Kai Germaschewski
2003-03-06 3:25 ` Daniel Egger
-- strict thread matches above, loose matches on Subject: below --
2003-03-06 14:22 Felipe Alfaro Solana
2003-03-06 19:51 ` Daniel Egger
2003-03-06 23:34 ` Andreas Boman
2003-03-06 23:44 ` Joel Becker
2003-03-07 13:33 ` Daniel Egger
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=20030305015957.GA27985@f00f.org \
--to=cw@f00f.org \
--cc=akpm@digeo.com \
--cc=degger@fhm.edu \
--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.