From: Justin Madru <jdm64@gawab.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: [Question] about modules/inline benefits
Date: Mon, 02 Jun 2008 21:13:13 -0700 [thread overview]
Message-ID: <4844C4D9.8030502@gawab.com> (raw)
Hi,
I've been compiling linus' git kernel (recompiling every -rc). I usually
compile many features/drivers as modules. I was wondering what the
benefits/drawbacks there are for modules compared to inlining.
What would be the differences between modules and inlining if you know
the hardware/features needed?
Is it better to not use modules if you're compiling for just one
computer that you know the hardware/features needed? (I know distros
have to use modules because they have to work on a wide variety of hardware)
Are there any performance/efficiency/memory benefits for inlining/module?
Are some drivers/features better suited to be compiled as modules?
Do modules slow down the boot process?
I currently have these modules:
i915
acpi_cpufreq
cpufreq_powersave
cpufreq_stats
cpufreq_userspace
cpufreq_conservative
container
sbs
sbshc
ext3
jbd
mbcache
arc4
ecb
crypto_blkcipher
rtc
dcdbas
cryptomgr
crypto_algapi
psmouse
evdev
snd_hda_intel
snd_pcm_oss
snd_mixer_oss
snd_pcm
iwl3945
mac80211
snd_timer
crc32
snd_page_alloc
video
backlight
output
ac
button
battery
intel_agp
reiserfs
sr_mod
cdrom
sg
ata_piix
ehci_hcd
uhci_hcd
usbcore
thermal
processor
fan
If inlining is more efficient/advantageous, then I might compile-in
everything I can, and use modules for testing new features and such.
Justin Madru
next reply other threads:[~2008-06-03 4:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 4:13 Justin Madru [this message]
2008-06-03 7:28 ` [Question] about modules/inline benefits Sitsofe Wheeler
2008-06-03 7:54 ` Oliver Neukum
2008-06-03 17:19 ` Adrian Bunk
2008-06-03 17:27 ` Adrian Bunk
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=4844C4D9.8030502@gawab.com \
--to=jdm64@gawab.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