Re: [PATCH 00/31] *** SUBJECT HERE ***

[Jean Delvare <khali@linux-fr.org>]

On Tue, 10 Mar 2009 16:23:48 +0000, Scott James Remnant wrote:
> module-init-tools on most distributions ships with a file that contains a
> large list of aliases to auto-load modules on demand, either by matching
> a MODALIAS string from the kernel uevent, or by the {block,char}-major-*
> aliases requested by the kernel when device nodes are opened.
> 
> There are convenient macros for defining these inside the kernel modules
> themselves, so they are exported by file2alias and put into the files
> created by depmod.  This is far preferable to a file in another package
> that has to be parsed every time modprobe is called (many, many times
> on a typical boot) and may get out of date.

I don't get how it could make any difference in terms of performance.
As far as I know, all the module aliases that come from the kernel are
assembled into /lib/modules/$version/modules.alias when the kernel is
installed, and that file must be processed by modprobe the exact same
way another configuration file would. Or am I missing something?

-- 
Jean Delvare