From: Steven Cole <elenstev@mesatop.com>
To: Robert Love <rml@tech9.net>
Cc: Andrew Morton <akpm@digeo.com>,
cw@f00f.org, degger@fhm.edu, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Kernel bloat 2.4 vs. 2.5
Date: 04 Mar 2003 20:13:46 -0700 [thread overview]
Message-ID: <1046834041.4114.32.camel@spc1.mesatop.com> (raw)
In-Reply-To: <1046831831.999.80.camel@phantasy.awol.org>
On Tue, 2003-03-04 at 19:37, Robert Love wrote:
> On Tue, 2003-03-04 at 21:32, Andrew Morton wrote:
>
> > well kallsyms is worth 150k.
> >
> > Do `strings vmlinux' and take a look at it all.
>
> Oh, yah. If he has kallsyms enabled that explains most of it.
>
> Robert Love
This shows what taking out kallsyms can do:
text data bss dec hex filename
1860575 293780 337404 2491759 26056f kernels/linux-2.4.18/vmlinux
1936720 311656 157792 2406168 24b718 BK/testing-2.5/vmlinux
1936592 437556 158720 2532868 26a604 BK/testing-2.5/vmlinux-with-kallsyms
The 2.5 tree was current yesterday.
The .config files were as "functionally equivalent" as I could make them,
and except for CONFIG_KALLSYMS, were identical for the two 2.5 images.
gcc is 2.96.
Steven
next prev parent reply other threads:[~2003-03-05 3:05 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
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 [this message]
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=1046834041.4114.32.camel@spc1.mesatop.com \
--to=elenstev@mesatop.com \
--cc=akpm@digeo.com \
--cc=cw@f00f.org \
--cc=degger@fhm.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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