From: Keith Owens <kaos@ocs.com.au>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: initdata for modules?
Date: Mon, 27 Nov 2000 09:54:57 +1100 [thread overview]
Message-ID: <1175.975279297@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Sun, 26 Nov 2000 07:30:44 -0800." <200011261530.HAA09799@baldur.yggdrasil.com>
On Sun, 26 Nov 2000 07:30:44 -0800,
"Adam J. Richter" <adam@yggdrasil.com> wrote:
> In reading include/linux/init.h, I was surprised to discover
>that __init{,data} expands to nothing when compiling a module.
>I was wondering if anyone is contemplating adding support for
>__init{,data} in module loading, to reduce the memory footprints
>of modules after they have been loaded.
It has been discussed a few times but nothing was ever done about it.
AFAIK the savings were not seen to be that important because modules
occupy complete pages. __init would have to be stored in a separate
page which was then discarded. It would complicate insmod, rmmod,
ksymoops and gdb. gdb against the kernel already gets confused by
vmlinux data that is discarded and gdb has problems with modules at the
best of times. Definitely 2.5 material, if at all.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-26 23:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-26 15:30 initdata for modules? Adam J. Richter
2000-11-26 22:54 ` Keith Owens [this message]
2000-11-27 0:01 ` Jeff V. Merkey
2000-11-26 23:45 ` Keith Owens
2000-11-27 2:45 ` Jeff V. Merkey
2000-11-27 7:35 ` Jakub Jelinek
-- strict thread matches above, loose matches on Subject: below --
2000-11-26 23:47 Adam J. Richter
2000-11-27 2:49 ` Jeff V. Merkey
2000-11-27 2:06 ` Keith Owens
2000-11-27 3:27 ` Jeff V. Merkey
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=1175.975279297@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=adam@yggdrasil.com \
--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