From: "Torsten Kaiser" <just.for.lkml@googlemail.com>
To: "Adrian Bunk" <bunk@kernel.org>
Cc: "Bodo Eggert" <7eggert@gmx.de>,
"Jan Engelhardt" <jengelh@computergmbh.de>,
devzero@web.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] Force UNIX domain sockets to be built in
Date: Mon, 31 Dec 2007 16:55:57 +0100 [thread overview]
Message-ID: <64bb37e0712310755k2446e67eq81d31cd476eb75e3@mail.gmail.com> (raw)
In-Reply-To: <20071231144255.GB13803@does.not.exist>
On Dec 31, 2007 3:42 PM, Adrian Bunk <bunk@kernel.org> wrote:
> With CONFIG_MODULES=y the 13 EXPORT_SYMBOL's that only exist for the
> theoretical possibility of CONIG_UNIX=m waste a few hundred bytes
> of memory.
One thing I always wondered about in this discussion about wasted
EXPORT_SYMBOL's:
Shouldn't it be possible to garbage collect these?
depmod already contains code to analyze all modules to create a
dependency tree. It should not be too difficult to extend it to create
a list of all symbols that really are used by the current modules.
Everything else could be stripped to save space.
The problem with that:
* out-of-tree modules would break if they don't get lucky to only use
the remaining symbol. I would not see this as a problem, if the help
text of the garbage-collect-option would contain a note like "don't
enable this if you want out-of-tree modules".
* if you later change your .config to include additional modules you
might need to rebuild vmlinux and reboot into the new kernel.
Currently you can probably build and load new modules without a
reboot. (for example: usb drivers)
Torsten
next prev parent reply other threads:[~2007-12-31 15:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-31 12:09 Bodo Eggert
2007-12-31 12:20 ` David Miller
2007-12-31 14:03 ` Bodo Eggert
2007-12-31 19:38 ` Al Viro
2008-01-01 3:45 ` Bodo Eggert
2008-01-01 3:48 ` David Miller
2008-01-01 4:48 ` Bodo Eggert
2008-01-01 5:01 ` Theodore Tso
2008-01-02 10:25 ` Herbert Xu
2008-01-02 12:26 ` Bodo Eggert
2007-12-31 12:24 ` Adrian Bunk
2007-12-31 13:26 ` Bodo Eggert
2007-12-31 14:42 ` Adrian Bunk
2007-12-31 15:19 ` Bodo Eggert
2007-12-31 15:34 ` Jan Engelhardt
2007-12-31 17:43 ` Patrick Mau
2007-12-31 22:20 ` Jan Engelhardt
2007-12-31 17:51 ` Adrian Bunk
2007-12-31 18:05 ` Adrian Bunk
2007-12-31 15:55 ` Torsten Kaiser [this message]
2007-12-31 15:59 ` Michael Buesch
2007-12-31 16:01 ` Alan Cox
2007-12-31 16:17 ` Torsten Kaiser
2007-12-31 16:38 ` Alan Cox
2007-12-31 17:18 ` Michael Buesch
2007-12-31 18:37 ` Torsten Kaiser
2007-12-31 19:05 ` Michael Buesch
2007-12-31 16:11 ` Torsten Kaiser
2007-12-31 13:23 devzero
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=64bb37e0712310755k2446e67eq81d31cd476eb75e3@mail.gmail.com \
--to=just.for.lkml@googlemail.com \
--cc=7eggert@gmx.de \
--cc=bunk@kernel.org \
--cc=devzero@web.de \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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
all inboxes | Powered by JetHome®