mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matt Heler <lkml@lpbproductions.com>
To: Scott Robert Ladd <coyote@coyotegulch.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Minimizing the Kernel
Date: Wed, 24 Sep 2003 09:39:01 -0700	[thread overview]
Message-ID: <200309240939.02316.lkml@lpbproductions.com> (raw)
In-Reply-To: <3F71C712.9070503@coyotegulch.com>

Well for starters dont use gcc 3 or above.. code size has increased 
dramatically with thoose versions. sure they give you more optimization , but 
if your looking for a small kernel use anything below 3..

Matt H.

On Wednesday 24 September 2003 09:32 am, Scott Robert Ladd wrote:
> I want to created the smallest, fastest kernel that supports all the
> necessary features of a given system.
>
> Obviously, the answer is very system dependent, requiring a keen
> knowledge of the relationships between hardware and Linux components.
>
> Unless I'm missing something (always a possibility), the kernel
> configurations do not provide a clear idea of component size. In other
> words, if I include "burfulgunk port support" in my kernel build, I'd
> like to have a rough idea of the component's size. I might not need to
> support the "burfulgunk", especially if it's a large component (for,
> say, a legacy port.)
>
> I'm well aware that code sizes differ between platforms; I'm looking for
> general information, as a guideline to generating a small kernel.

  reply	other threads:[~2003-09-24 16:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-24 16:32 Scott Robert Ladd
2003-09-24 16:39 ` Matt Heler [this message]
2003-09-24 17:13   ` Maciej Soltysiak
2003-09-24 18:21     ` Valdis.Kletnieks
2003-09-24 17:32 Andrzej Krzysztofowicz
2003-09-24 22:39 ` Timothy Miller
2003-09-25  2:22 rwhron
2003-09-25  4:54 rwhron

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=200309240939.02316.lkml@lpbproductions.com \
    --to=lkml@lpbproductions.com \
    --cc=coyote@coyotegulch.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

all inboxes | Powered by JetHome®