From: Andrew Morton <akpm@zip.com.au>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Linux-Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: PATCH 2.4.17.2: make ext2 smaller
Date: Sun, 02 Dec 2001 13:30:53 -0800 [thread overview]
Message-ID: <3C0A9D8D.4CC463A0@zip.com.au> (raw)
In-Reply-To: <3C0A1105.18B76D64@mandrakesoft.com>
Jeff Garzik wrote:
>
> Results from 2.4.17-pre2 plus the attached patch: 1135 bytes saved in
> vmlinux, simply from making all the functions static.
> (*.orig is prior to my patch. kernel is P2 SMP-based)
> > [jgarzik@rum linux-e2all]$ ls -l vmlinux* arch/i386/boot/bzImage*
> > -rw-r--r-- 1 jgarzik jgarzik 1030259 Dec 2 06:18 arch/i386/boot/bzImage
> > -rw-r--r-- 1 jgarzik jgarzik 1030263 Dec 2 06:04 arch/i386/boot/bzImage.orig
> > -rwxr-xr-x 1 jgarzik jgarzik 2814631 Dec 2 06:18 vmlinux*
> > -rwxr-xr-x 1 jgarzik jgarzik 2815766 Dec 2 06:04 vmlinux.orig*
>
but, but, but... That's on-disk size.
What does /usr/bin/size say?
And don't forget http://www.zip.com.au/~akpm/linux/2.4/2.4.17-pre1/inline.patch
which deletes 61 `inline's and save 12 kbytes. We really, really
need to examine our use of inlines. It's probable that we're
sloshing squigabytes of instructions across the external memory bus
quite unnecessarily.
-
next prev parent reply other threads:[~2001-12-02 21:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-02 11:31 PATCH 2.4.17.2: make ext2 smaller Jeff Garzik
2001-12-02 11:54 ` Keith Owens
2001-12-02 12:33 ` Ingo Oeser
2001-12-02 13:00 ` PATCH 2.4.17.2: CONFIG_FINAL, make kernel smaller Jeff Garzik
2001-12-02 13:07 ` Jeff Garzik
2001-12-02 13:03 ` PATCH 2.4.17.2: make ext2 smaller Jeff Garzik
2001-12-02 13:40 ` Ingo Oeser
2001-12-02 13:47 ` Jeff Garzik
2001-12-02 13:53 ` Ingo Oeser
2001-12-02 16:14 ` Christer Weinigel
2001-12-02 16:44 ` Martin Dalecki
2001-12-02 17:42 ` Jeff Garzik
2001-12-02 21:30 ` Andrew Morton [this message]
2001-12-02 21:35 ` Jeff Garzik
2001-12-03 2:53 ` Horst von Brand
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=3C0A9D8D.4CC463A0@zip.com.au \
--to=akpm@zip.com.au \
--cc=jgarzik@mandrakesoft.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