From: Matt Mackall <mpm@selenic.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org, zwane@linuxpower.ca
Subject: Re: [PATCH] Drop exported symbols list if !modules
Date: Mon, 5 Apr 2004 18:36:24 -0500 [thread overview]
Message-ID: <20040405233624.GL6248@waste.org> (raw)
In-Reply-To: <20040405163019.4e3ab546.akpm@osdl.org>
On Mon, Apr 05, 2004 at 04:30:19PM -0700, Andrew Morton wrote:
> Rusty Russell <rusty@rustcorp.com.au> wrote:
> >
> > On Tue, 2004-04-06 at 09:07, Matt Mackall wrote:
> > > On Tue, Apr 06, 2004 at 08:45:01AM +1000, Rusty Russell wrote:
> > > > On Tue, 2004-04-06 at 06:55, Matt Mackall wrote:
> > > > > Drop ksyms if we've built without module support
> > > > >
> > > > > From: Zwane Mwaikambo <zwane@arm.linux.org.uk>
> > > > > Subject: Re: 2.6.1-rc1-tiny2
> > > >
> > > > Other than saving a little compile time, does this actually do anything?
> > > >
> > > > I'm not against it, I just don't think I see the point.
> > >
> > > Well it obviously saves memory and image size too;
> >
> > Please measure it. It's not obvious to me at all.
>
> Miniscule savings
>
> text data bss dec hex filename
> 3221815 862456 0 4084271 3e522f vmlinux-before
> 3221591 862456 0 4084047 3e514f vmlinux-after
I was seeing this when I added it to my tree circa 2.6.1:
701262 58619 15616 775497 bd549 vmlinux before
700530 58619 15616 774765 bd26d vmlinux after
..which I would expect to grow with code size.
On the other hand, I'm now seeing:
0 0 0 0 0 arch/i386/kernel/i386_ksyms.o
So something's changed.
--
Matt Mackall : http://www.selenic.com : Linux development and consulting
next prev parent reply other threads:[~2004-04-05 23:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 20:55 Matt Mackall
2004-04-05 22:45 ` Rusty Russell
2004-04-05 23:07 ` Matt Mackall
2004-04-05 23:17 ` Rusty Russell
2004-04-05 23:30 ` Andrew Morton
2004-04-05 23:36 ` Matt Mackall [this message]
2004-04-06 0:48 ` Rusty Russell
2004-04-05 23:49 ` Brian Gerst
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=20040405233624.GL6248@waste.org \
--to=mpm@selenic.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=zwane@linuxpower.ca \
/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
all inboxes | Powered by JetHome®