public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Linux-Kernel list <linux-kernel@vger.kernel.org>
Cc: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
	Keith Owens <kaos@ocs.com.au>
Subject: PATCH 2.4.17.2: CONFIG_FINAL, make kernel smaller
Date: Sun, 02 Dec 2001 08:00:57 -0500	[thread overview]
Message-ID: <3C0A2609.AB42C366@mandrakesoft.com> (raw)
In-Reply-To: <3C0A1105.18B76D64@mandrakesoft.com> <25560.1007294074@ocs3.intra.ocs.com.au> <20011202133314.B717@nightmaster.csn.tu-chemnitz.de>

Ingo Oeser wrote:
> On Sun, Dec 02, 2001 at 10:54:34PM +1100, Keith Owens wrote:
> > On Sun, 02 Dec 2001 06:31:17 -0500,
> > Jeff Garzik <jgarzik@mandrakesoft.com> wrote:
> > >Simply, all ext2 files are #include'd into a single file, ext2_all.c,
> > >and all functions and data structures are declared static.
> >
> > I like it.
> 
> Me also. Except for the KSTATIC spread all over the Kernel.

Yes :/  The source code is definitely uglier.  Maybe 'kstatic' would be
better on the eyes.

I just converted reiserfs and linux/kernel directories to KSTATIC.
ftp://ftp.kernel.org/pub/linux/kernel/people/jgarzik/patches/2.4.17/config-final-2.4.17.2.patch.gz 
(should appear on ftp.kernel.org and mirrors soon, if not already)

Bytes saved/eliminated:
	ext2:		1135
	reiserfs:	2966
	kernel:		2578

	total:		6679 bytes saved

The conversion of linux/kernel was surprising...  I only changed two
'int' variables to KSTATIC.  That implies to me that the majority of the
space savings might simply come from the better packing created when
compiling all the files into a single .o.

I would like to also point out a nice fringe benefit:  since an entire
subsystem/driver is compiled together, you find bugs.  I have found
[tiny, unimportant] bugs in all the code I have converted to KSTATIC so
far.

> [jgarzik@rum linux-e2all]$ ls -l vmlinux* arch/i386/boot/bzImage*
> -rw-r--r--    1 jgarzik  jgarzik   1030123 Dec  2 07:50 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   2809087 Dec  2 07:50 vmlinux*
> -rwxr-xr-x    1 jgarzik  jgarzik   2815766 Dec  2 06:04 vmlinux.orig*

-- 
Jeff Garzik      | Only so many songs can be sung
Building 1024    | with two lips, two lungs, and one tongue.
MandrakeSoft     |         - nomeansno


  reply	other threads:[~2001-12-02 13:01 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     ` Jeff Garzik [this message]
2001-12-02 13:07       ` PATCH 2.4.17.2: CONFIG_FINAL, make kernel smaller 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
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=3C0A2609.AB42C366@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=kaos@ocs.com.au \
    --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