From: Scott James Remnant <scott-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
To: maximilian attems <max-U9r9yeDMy7A@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kernel-team-nLRlyDuq1AZFpShjVBNYrg@public.gmane.org,
debian-kernel-0aAXYlwwYIJuHlm7Suoebg@public.gmane.org
Subject: Re: initramfs-tools stable release 0.93.3
Date: Thu, 11 Jun 2009 11:42:07 +0100 [thread overview]
Message-ID: <1244716927.4532.34.camel@quest> (raw)
In-Reply-To: <20090610153017.GA19401-U9r9yeDMy7A@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
On Wed, 2009-06-10 at 17:30 +0200, maximilian attems wrote:
> hook-functions: Add i915 module for kms.
>
This is exactly the kind of bloat I want to avoid for the initramfs.
The initramfs should do one thing only, that's mount the root filesystem
and chain load into it.
Anything else is an extravagance.
Why load the KMS driver in the initramfs? Because it takes too long to
get to the point in the real system where we can load it! Why does it
take too long to get there? Because we spend so long in the initramfs!
Slimming the initramfs right down to the essentials reduces the boot
time by over a second! Paradoxically, this means that the driver can be
loaded in the real system at roughly the same time point as it would be
loaded in a bloated initramfs.
Scott
--
Scott James Remnant
scott-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-06-11 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 15:30 initramfs-tools stable release 0.93.3 maximilian attems
[not found] ` <20090610153017.GA19401-U9r9yeDMy7A@public.gmane.org>
2009-06-11 10:42 ` Scott James Remnant [this message]
2009-07-25 9:21 ` maximilian attems
[not found] ` <20090725092159.GJ11967-U9r9yeDMy7A@public.gmane.org>
2009-07-29 12:44 ` Scott James Remnant
2009-08-07 7:37 ` Seewer Philippe
[not found] ` <4A7BD9B4.1090109-omB+W0Dpw2o@public.gmane.org>
2009-08-07 14:00 ` Alan Jenkins
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=1244716927.4532.34.camel@quest \
--to=scott-gewih/nmzzlqt0dzr+alfa@public.gmane.org \
--cc=debian-kernel-0aAXYlwwYIJuHlm7Suoebg@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kernel-team-nLRlyDuq1AZFpShjVBNYrg@public.gmane.org \
--cc=max-U9r9yeDMy7A@public.gmane.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