All of lore.kernel.org
 help / color / mirror / Atom feed
From: mru@kth.se (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: Why are 2.6 modules so huge?
Date: Wed, 25 Feb 2004 09:56:41 +0100	[thread overview]
Message-ID: <yw1xd683fsfq.fsf@kth.se> (raw)
In-Reply-To: 403C4E98.6010107@t-online.de

Harald Dunkel <harald.dunkel@t-online.de> writes:

> Måns Rullgård wrote:
>> My 2.6.3 vfat.ko is 15365 bytes.  Maybe you enabled kernel debugging
>> symbols.
>>
>
> % ll /lib/modules/2.6.3/kernel/fs/vfat/
> total 16
> -rw-r--r--    1 root     root        14232 Feb 19 07:43 vfat.ko
>
> Assuming that you are on i686:
>
> A size difference of 1 KByte (about 7%) is remarkable. Which
> gcc did you use for building 2.6.3?

I used gcc 3.3.2.  Here's an objdump -h of that file:

/lib/modules/2.6.3/kernel/fs/vfat/vfat.ko:     file format elf32-i386

Sections:
Idx Name          Size      VMA       LMA       File off  Algn
  0 .text         0000209c  00000000  00000000  00000034  2**2
                  CONTENTS, ALLOC, LOAD, RELOC, READONLY, CODE
  1 .init.text    00000013  00000000  00000000  000020d0  2**0
                  CONTENTS, ALLOC, LOAD, RELOC, READONLY, CODE
  2 .exit.text    00000013  00000000  00000000  000020e3  2**0
                  CONTENTS, ALLOC, LOAD, RELOC, READONLY, CODE
  3 .rodata.str1.1 0000004c  00000000  00000000  000020f6  2**0
                  CONTENTS, ALLOC, LOAD, READONLY, DATA
  4 .rodata.str1.32 00000073  00000000  00000000  00002160  2**5
                  CONTENTS, ALLOC, LOAD, READONLY, DATA
  5 __ksymtab_strings 00000046  00000000  00000000  000021d3  2**0
                  CONTENTS, ALLOC, LOAD, READONLY, DATA
  6 __ksymtab     00000030  00000000  00000000  0000221c  2**2
                  CONTENTS, ALLOC, LOAD, RELOC, READONLY, DATA
  7 .modinfo      00000059  00000000  00000000  00002260  2**5
                  CONTENTS, ALLOC, LOAD, READONLY, DATA
  8 .data         00000120  00000000  00000000  000022c0  2**5
                  CONTENTS, ALLOC, LOAD, RELOC, DATA
  9 .gnu.linkonce.this_module 00000200  00000000  00000000  00002400  2**7
                  CONTENTS, ALLOC, LOAD, RELOC, DATA, LINK_ONCE_DISCARD
 10 .bss          00000000  00000000  00000000  00002600  2**2
                  ALLOC
 11 .comment      00000036  00000000  00000000  00002600  2**0
                  CONTENTS, READONLY


-- 
Måns Rullgård
mru@kth.se


  reply	other threads:[~2004-02-25  8:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-24 15:30 Why are 2.6 modules so huge? Ian Soboroff
2004-02-24 15:40 ` Norberto Bensa
2004-02-24 15:46 ` Måns Rullgård
2004-02-25  7:28   ` Harald Dunkel
2004-02-25  8:56     ` Måns Rullgård [this message]
2004-02-24 15:50 ` Brian Gerst
2004-02-24 16:03   ` Ian Soboroff
2004-02-24 15:50 ` Jan De Luyck
2004-02-24 16:05 ` James Morris

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=yw1xd683fsfq.fsf@kth.se \
    --to=mru@kth.se \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.