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: Wed, 29 Jul 2009 13:44:31 +0100 [thread overview]
Message-ID: <1248871471.23840.50.camel@quest> (raw)
In-Reply-To: <20090725092159.GJ11967-U9r9yeDMy7A@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1985 bytes --]
On Sat, 2009-07-25 at 11:21 +0200, maximilian attems wrote:
> On Thu, 11 Jun 2009, Scott James Remnant wrote:
>
> > 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.
>
> well it is useful to resume or to load acpi modules early so boxes don't
> overheat.
>
If you don't include them in the initramfs, your initramfs will be
smaller so quicker to load, decompress and unpack. If you then load
them immediately after mounting the root filesystem, will they be loaded
(a) sooner or (b) later than before?
Research tends to suggest (a)
If you skip the initramfs, how are they loaded otherwise? In some cases
they may never be loaded at all! In others, they're loaded by udev -
which is used in the initramfs as well, so why force load them?
> also there are quite some different scenarios your root can be
> on.
>
While true, changing the root format is a software configuration change
not a hardware configuration change. Changing to/from software RAID,
LVM, encrypted root, etc. is all a major enough change (including fstab,
as well as raid config files, etc.) that it's ok to need to update your
initramfs to include the necessary changes.
This is very different from changing your storage controller card.
> > 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.
>
> well afair the intel fast boot doesn't use initramfs in the fast path
> at all
>
Our fast boot does use an 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-07-29 12:44 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
2009-07-25 9:21 ` maximilian attems
[not found] ` <20090725092159.GJ11967-U9r9yeDMy7A@public.gmane.org>
2009-07-29 12:44 ` Scott James Remnant [this message]
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=1248871471.23840.50.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.