Hm, I think you're a bit confused here.
/sbin/hotplug has nothing to do with modules. It works just fine with a
kernel with everything built in. /sin/hotplug is getting called when
anything in the system changes, like a device is discovered or removed.
Now the fact that the current hotplug package that implements a version
of /sbin/hotplug only really handles loading new modules for devices
that do not currently have drivers bound to them, is only an
implementation detail. The hotplug package will start to change soon,
based on the new information that is being spit out by your kernel.
> given that we had a patch a week or so ago to change how modules get
> loaded into memory to avoid a 'several percentage point' speed difference
> between modules and built-in and that the people pushing 'do everything in
> initramfs' have been saying for years that there is no performance
> difference I for one am not convinced that mandating initramfs is a good
> thing.
initramfs and "everything must be a module" are two different
discussions. Only after the first happens can we even start talking
about the second.
And even if we don't ever agree that everything has to be a module, the
initramfs implementation moves a whole lot of crap out of kernel space,
and into userspace, that I can't see any good reason not to have it.
But let's wait for Al's latest initramfs patches to start talking about
that topic, I thought this thread was about evms :)
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/