mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org, mm-commits@vger.kernel.org, rossb@google.com,
	akpm@google.com, sam@ravnborg.org
Subject: Re: + allow-proc-configgz-to-be-built-as-a-module.patch added to -mm tree
Date: Fri, 15 Sep 2006 15:47:52 -0700	[thread overview]
Message-ID: <20060915154752.d7bdb8a0.rdunlap@xenotime.net> (raw)
In-Reply-To: <200609152158.k8FLw7ud018089@shell0.pdx.osdl.net>

On Fri, 15 Sep 2006 14:58:06 -0700 akpm@osdl.org wrote:

> 
> The patch titled
> 
>      allow /proc/config.gz to be built as a module
> 
> has been added to the -mm tree.  Its filename is
> 
>      allow-proc-configgz-to-be-built-as-a-module.patch
> 
> See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
> out what to do about this
> 
> ------------------------------------------------------
> Subject: allow /proc/config.gz to be built as a module
> From: Ross Biro <rossb@google.com>

When/where was this patch submitted?  I seem to have missed it
(or it was so long ago that I forgot about it).

> The driver for /proc/config.gz consumes rather a lot of memory and it is in
> fact possible to build it as a module.

Can you try to quantify "rather a lot of memory"?

> 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.

and that's why a module wasn't allowed.
It's not worth the risk IMO.

> But OTOH the potential memory savings are decent, and it'd be fairly dumb to
> build your configs.o with a different .config.
> 
> Signed-off-by: Andrew Morton <akpm@google.com>
> Cc: "Randy.Dunlap" <rdunlap@xenotime.net>
> Cc: Sam Ravnborg <sam@ravnborg.org>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> ---
> 
>  init/Kconfig |    2 +-
>  1 files changed, 1 insertion(+), 1 deletion(-)
> 
> diff -puN init/Kconfig~allow-proc-configgz-to-be-built-as-a-module init/Kconfig
> --- a/init/Kconfig~allow-proc-configgz-to-be-built-as-a-module
> +++ a/init/Kconfig
> @@ -241,7 +241,7 @@ config AUDITSYSCALL
>  	  ensure that INOTIFY is configured.
>  
>  config IKCONFIG
> -	bool "Kernel .config support"
> +	tristate "Kernel .config support"
>  	---help---
>  	  This option enables the complete Linux kernel ".config" file
>  	  contents to be saved in the kernel. It provides documentation
> _

---
~Randy

       reply	other threads:[~2006-09-15 22:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200609152158.k8FLw7ud018089@shell0.pdx.osdl.net>
2006-09-15 22:47 ` Randy.Dunlap [this message]
2006-09-15 23:04   ` rossb
2006-09-15 23:11     ` Randy.Dunlap
2006-09-15 23:41   ` Andrew Morton
2006-09-16  0:14     ` Randy.Dunlap
2006-09-16  0:23     ` Olivier Galibert
2006-09-16  0:33     ` Adrian Bunk
2006-10-02  1:17     ` Randy Dunlap
2006-10-02  6:32       ` Olaf Hering
2006-09-16 11:47   ` Arjan van de Ven
2006-09-17  0:48     ` rossb
2006-09-17  1:13       ` Adrian Bunk
2006-10-02  7:08 Mikael Pettersson
2006-10-02 10:42 ` Olivier Galibert
2006-10-02 11:23 Mikael Pettersson

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=20060915154752.d7bdb8a0.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@google.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=rossb@google.com \
    --cc=sam@ravnborg.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

Powered by JetHome