From: Scott Robert Ladd <coyote@coyotegulch.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Minimizing the Kernel
Date: Wed, 24 Sep 2003 12:32:18 -0400 [thread overview]
Message-ID: <3F71C712.9070503@coyotegulch.com> (raw)
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.
--
Scott Robert Ladd
Coyote Gulch Productions (http://www.coyotegulch.com)
Software Invention for High-Performance Computing
next reply other threads:[~2003-09-24 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 16:32 Scott Robert Ladd [this message]
2003-09-24 16:39 ` Minimizing the Kernel Matt Heler
2003-09-24 17:13 ` Maciej Soltysiak
2003-09-24 18:21 ` Valdis.Kletnieks
-- strict thread matches above, loose matches on Subject: below --
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=3F71C712.9070503@coyotegulch.com \
--to=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