From: Christoph Hellwig <hch@infradead.org>
To: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: [bernie@develer.com: Kernel 2.6 size increase]
Date: Wed, 23 Jul 2003 19:53:55 +0100 [thread overview]
Message-ID: <20030723195355.A27597@infradead.org> (raw)
I think this is not only of interest fir the uClinux folks..
----- Forwarded message from Bernardo Innocenti <bernie@develer.com> -----
Date: Wed, 23 Jul 2003 20:46:46 +0200
From: Bernardo Innocenti <bernie@develer.com>
Subject: Kernel 2.6 size increase
To: uClinux development list <uclinux-dev@uclinux.org>
Cc: linux-kernel@vger.kernel.org
Hello,
code bloat can be very harmful on embedded targets, but it's
generally inconvenient for any platform. I've measured the
code increase between 2.4.21 and 2.6.0-test1 on a small
kernel configuration for ColdFire:
text data bss dec hex filename
640564 39152 134260 813976 c6b98 linux-2.4.x/linux
845924 51204 78896 976024 ee498 linux-2.5.x/vmlinux
I could provide the exact .config file for both kernels to
anybody interested. They are almost the same: no filesystems
except JFFS2, IPv4 and a bunch of small drivers. I have no
SMP, security, futexes, modules and anything else not
strictly needed to execute processes.
I've made a linker map file and compared the size of single
subsystems. These are the the major contributors to the
size increase:
kernel/ +27KB
mm/ +14KB
fs/ +47KB
drivers/ +35KB
net/ +64KB
I've digged into net/ with nm -S --size-sort. It seems that
the major increase is caused by net/xfrm/. Could this module
be made optional?
In fs/, almost all modules have got 30-40% bigger, therefore
bloat is probably caused by inlines and macros getting more
complex.
Block drivers and MTD have generally become smaller. Character
devices are responsable for most of the size increase in drivers/.
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
Please don't send Word attachments - http://www.gnu.org/philosophy/no-word-attachments.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
----- End forwarded message -----
next reply other threads:[~2003-07-23 18:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 18:53 Christoph Hellwig [this message]
2003-07-23 18:55 ` [bernie@develer.com: Kernel 2.6 size increase] Christoph Hellwig
2003-07-23 18:58 ` David S. Miller
[not found] ` <20030723115858.7506829I4.davem@redhat.com>
2003-07-23 19:06 ` Christoph Hellwig
2003-07-23 19:09 ` David S. Miller
2003-07-23 19:13 ` Christoph Hellwig
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=20030723195355.A27597@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).