public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Daniel Egger <degger@fhm.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel bloat 2.4 vs. 2.5
Date: Tue, 4 Mar 2003 15:41:05 -0800	[thread overview]
Message-ID: <20030304154105.7a2db7fa.akpm@digeo.com> (raw)
In-Reply-To: <1046817738.4754.33.camel@sonja>

Daniel Egger <degger@fhm.edu> wrote:
>
> Hija,
> 
> I've seen surprisingly few messages about the dramatic size increase
> between a simple 2.4 and a 2.5 kernel image. 
> 
> I just decided to check back with the 2.5 series again after my last try
> with 2.5.53 (which wouldn't even boot) but had to dramatically cut down
> the kernel featurewise to keep it below 1MB because I can't boot it over
> tftp otherwise. 
> 
> 909824 Feb 14 20:02 vmlinuz-192.168.11.3-2.4.20
> 954880 Mar  4 17:01 vmlinuz-192.168.11.3-2.5.63

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.

Please specify the compiler which was used, and use /usr/bin/size to report
image sizes.



  reply	other threads:[~2003-03-04 23:34 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 [this message]
2003-03-05  1:59   ` Chris Wedgwood
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=20030304154105.7a2db7fa.akpm@digeo.com \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox