From: Randy Dunlap <rdunlap@xenotime.net>
To: akpm@osdl.org, lkml <linux-kernel@vger.kernel.org>
Cc: torvalds@osdl.org, rossb@google.com, akpm@google.com, sam@ravnborg.org
Subject: Re: [patch 024/144] allow /proc/config.gz to be built as a module
Date: Sun, 1 Oct 2006 09:39:54 -0700 [thread overview]
Message-ID: <20061001093954.8d2aa064.rdunlap@xenotime.net> (raw)
In-Reply-To: <200610010627.k916RPIs010370@shell0.pdx.osdl.net>
On Sat, 30 Sep 2006 23:27:25 -0700 akpm@osdl.org wrote:
> From: Ross Biro <rossb@google.com>
>
> The driver for /proc/config.gz consumes rather a lot of memory and it is in
> fact possible to build it as a module.
>
> In some ways this is a bit risky, because the .config which is used for
> compiling kernel/configs.c isn't necessarily the same as the .config which was
> used to build vmlinux.
>
> But OTOH the potential memory savings are decent, and it'd be fairly dumb to
> build your configs.o with a different .config.
so after getting several disagreements on this, you are going ahead
with it. I'm disappointed, but I agree that you have a right to
do so. (IOW, I wouldn't be disappointed if some other patches
were merged even though someone disapproved of them :)
And the memory savings are not a big deal. You even mentioned that
you had it confused with /proc/kallsyms.
---
~Randy
next parent reply other threads:[~2006-10-01 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200610010627.k916RPIs010370@shell0.pdx.osdl.net>
2006-10-01 16:39 ` Randy Dunlap [this message]
2006-10-01 18:36 ` Andrew Morton
2006-10-01 18:52 ` Randy Dunlap
2006-10-02 14:09 ` Ross Biro
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=20061001093954.8d2aa064.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@google.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rossb@google.com \
--cc=sam@ravnborg.org \
--cc=torvalds@osdl.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®