From: Harald Dunkel <harald.dunkel@t-online.de>
To: "Måns Rullgård" <mru@kth.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why are 2.6 modules so huge?
Date: Wed, 25 Feb 2004 08:28:24 +0100 [thread overview]
Message-ID: <403C4E98.6010107@t-online.de> (raw)
In-Reply-To: <yw1x1xokcwfo.fsf@kth.se>
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 am on Debian (Sid). Gcc is 3.3.3, which was released a
few days ago.
Regards
Harri
next prev parent reply other threads:[~2004-02-25 7:28 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 [this message]
2004-02-25 8:56 ` Måns Rullgård
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=403C4E98.6010107@t-online.de \
--to=harald.dunkel@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@kth.se \
/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