From: Oliver Neukum <oliver@neukum.name>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Gerd Hoffmann <kraxel@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: blacklist kernel boot option
Date: Mon, 29 Jan 2007 14:38:22 +0100 (MET) [thread overview]
Message-ID: <200701291438.25400.oliver@neukum.name> (raw)
In-Reply-To: <Pine.LNX.4.61.0701291412300.5077@yvahk01.tjqt.qr>
Am Montag, 29. Januar 2007 14:23 schrieb Jan Engelhardt:
>
> On Jan 29 2007 13:44, Oliver Neukum wrote:
> >What use is it to modularly compile something that almost everybody needs?
>
> [correction: meant CONFIG_BLK_DEV_MD, because CONFIG_MD itself does
> not generate any code]
>
> So just because almost everyone needs CONFIG_SCSI (SATA, usb_storage,
> you name it), you're going to compile that in as well? It's just
> another 180 KB [BLK_DEV_MD: ~100K] so let's compile it in!
For every module you waste PAGE_SIZE/2. In my system
oliver@valisk:~/Desktop/linux-2.6.20-6-greg> lsmod|wc
46 158 1827
that's 92K. There is a point where the number of people who don't
need it grows too small to justify that.
> There is a reason initramfs exists, and it's not only for firmware
> loading or running custom scripts.
But shrinking the statically compiled kernel isn't one of them. You need
to look at the actual memory footprint.
Regards
Oliver
prev parent reply other threads:[~2007-01-29 13:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-27 1:22 blacklist kernel boot option Florian Schmidt
2007-01-27 14:53 ` Jan Engelhardt
2007-01-27 17:18 ` Bernhard Walle
2007-01-29 8:30 ` Gerd Hoffmann
2007-01-29 11:12 ` Jan Engelhardt
2007-01-29 11:25 ` Gerd Hoffmann
2007-01-29 12:40 ` Jan Engelhardt
2007-01-29 12:44 ` Oliver Neukum
2007-01-29 13:23 ` Jan Engelhardt
2007-01-29 13:38 ` Oliver Neukum [this message]
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=200701291438.25400.oliver@neukum.name \
--to=oliver@neukum.name \
--cc=jengelh@linux01.gwdg.de \
--cc=kraxel@suse.de \
--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