From: Brian Gerst <bgerst@didntduck.org>
To: Matt Mackall <mpm@selenic.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Zwane Mwaikambo <zwane@linuxpower.ca>
Subject: Re: [PATCH] Drop exported symbols list if !modules
Date: Mon, 05 Apr 2004 19:49:18 -0400 [thread overview]
Message-ID: <4071F07E.2040307@quark.didntduck.org> (raw)
In-Reply-To: <20040405230723.GK6248@waste.org>
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; I'm in the process
> of merging bits from my -tiny tree. As bloat has a way of being
> well-distributed across the code base, it's going to take many small
> trimmings to cut it back. Most of the 150 or so patches I've got now
> save between 1 and 8k. Doesn't sound like much, but it adds up.
>
EXPORT_SYMBOL() is a no-op when modules are disabled:
$ size arch/i386/kernel/i386_ksyms.o
text data bss dec hex filename
0 0 0 0 0 arch/i386/kernel/i386_ksyms.o
Although, what really should be done is to move the exports to the
appropriate files instead of keeping them lumped together.
--
Brian Gerst
prev parent reply other threads:[~2004-04-05 23:53 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
2004-04-06 0:48 ` Rusty Russell
2004-04-05 23:49 ` Brian Gerst [this message]
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=4071F07E.2040307@quark.didntduck.org \
--to=bgerst@didntduck.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--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®