mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Kyle McMartin <kyle@canonical.com>
Cc: Christoph Pleger <Christoph.Pleger@cs.uni-dortmund.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Size of kernel modules
Date: Fri, 8 Jun 2007 08:40:22 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0706080838210.17480@localhost.localdomain> (raw)
In-Reply-To: <20070608034421.GM26717@fattire.cabal.ca>

On Thu, 7 Jun 2007, Kyle McMartin wrote:

> On Wed, Jun 06, 2007 at 05:05:34PM +0200, Christoph Pleger wrote:
> > So, my question is the follwing: Is it an expected feature that the file
> > sizes of modules grow so much only because of a different cpu type and a
> > different localversion, or is there probably a bug in my build tools?
>
> The kernel is compiled with debug info so that we can strip it later to
> build two packages, one with debugging information intact, and one
> without it.
>
> If you disable CONFIG_DEBUG_KERNEL, things should go back to normal
> sizes for you.

grow so much compared to *which other modules*?  the ones that came
with your distro?  if that's the case, try installing your new modules
with

  # make INSTALL_MOD_STRIP=1 modules_install

that makes a *huge* difference in the size of the installed modules,
as i learned when i first ran across this on my fedora core system.

rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================

  reply	other threads:[~2007-06-08 12:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 15:05 Christoph Pleger
2007-06-06 15:51 ` Jesper Juhl
2007-06-06 16:56   ` Jan Engelhardt
2007-06-06 17:17   ` Sam Ravnborg
2007-06-06 15:59 ` jimmy bahuleyan
2007-06-06 17:22 ` Sam Ravnborg
2007-06-06 18:40 ` Joseph Fannin
2007-06-08  3:44 ` Kyle McMartin
2007-06-08 12:40   ` Robert P. J. Day [this message]
2007-06-08 18:59     ` Chuck Ebbert
2007-06-09  7:55     ` Jan Engelhardt
2007-06-09 12:08       ` Jon Masters
2007-06-09 13:59         ` Jan Engelhardt
2007-06-09 16:14           ` Jon Masters
2007-06-09 18:56           ` Satyam Sharma
2007-06-10 13:13           ` Sergey Vlasov

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=Pine.LNX.4.64.0706080838210.17480@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=Christoph.Pleger@cs.uni-dortmund.de \
    --cc=kyle@canonical.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

all inboxes | Powered by JetHome®