From: John Reiser <jreiser-Po6cBsTGB2ZWk0Htik3J/w@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: build initramfs: explain modprobe?
Date: Tue, 30 Aug 2011 15:48:00 -0700 [thread overview]
Message-ID: <4E5D68A0.8020006@bitwagon.com> (raw)
What properties of modprobe are essential for building initramfs?
Modprobe works for only one kernel module at a time, and this is
a cause of slowness. For instance, computing the transitive
closure of the Requires relationship over a non-small set of modules
can be performed faster by loading modules.dep into a bash associative
array, then processing in bash. Also, modinfo now is invoked once per
module to find firmware, but this can be sped up by invoking on batches
of modules, using "split -C 32000" to avoid the argsize limit of execve.
Invoking modprobe with --ignore-install seems to remove any effects
due to (possibly host-specific) /etc/modules.d/*.conf. Is there anything
else that modprobe does for building initramfs, other than transitive
closure of Requires?
--
next reply other threads:[~2011-08-30 22:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 22:48 John Reiser [this message]
[not found] ` <4E5D68A0.8020006-Po6cBsTGB2ZWk0Htik3J/w@public.gmane.org>
2011-08-31 12:15 ` build initramfs: explain modprobe? Harald Hoyer
[not found] ` <4E5E25DA.4060802-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-09-06 15:34 ` John Reiser
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=4E5D68A0.8020006@bitwagon.com \
--to=jreiser-po6cbstgb2zwk0htik3j/w@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@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