public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: module choices affecting base kernel size???
Date: Fri, 03 May 2002 11:28:57 +1000	[thread overview]
Message-ID: <3271.1020389337@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Thu, 02 May 2002 20:57:40 -0400." <Pine.LNX.4.44.0205022054160.8024-100000@conn6m.toms.net>

On Thu, 2 May 2002 20:57:40 -0400 (EDT), 
Tom Oehser <tom@toms.net> wrote:
>
>> Tom Oehser <tom@toms.net> wrote:
>> >Changing all =m to =n in my config makes a 4K difference in the kernel size.
>
>On Fri, 3 May 2002, Keith Owens wrote:
>
>> The majority of modules have no effect on kernel size but some modules
>> require base kernel code as well.  This is typically common code or low
>> level setup functions.  You will find that those modules will not load
>> now or will break.
>
>Great.  I must have missed the list of exactly *which* modules do this...
>
>Any ideas on a reasonable way of how to identify them?

Not easy.  Some of it is in the Makefiles, some of it is in the code.
Looking for conditional EXPORT_SYMBOLS() will find some of the extra
space, I don't know of any way of finding all of the extra code/data,
apart from compiling and measuring.


  parent reply	other threads:[~2002-05-03  1:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-02 14:49 module choices affecting base kernel size??? Tom Oehser
2002-05-02 23:58 ` Keith Owens
2002-05-03  0:57   ` Tom Oehser
2002-05-03  0:01     ` Martin Dalecki
2002-05-03  1:28     ` Keith Owens [this message]
2002-05-03 15:03     ` David Woodhouse

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=3271.1020389337@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --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