Re: [PATCH -next 00/11] remove CONFIG_KMOD

[Rusty Russell <rusty@rustcorp.com.au>]

On Monday 14 July 2008 01:03:02 Andi Kleen wrote:
> Johannes Berg <johannes@sipsolutions.net> writes:
> > I've rebased this patch series against -next-20080708 (one conflict
> > against ftrace, another against BKL pushdown) and fixed the things
> > Adrian Bunk pointed out.
>
> You forgot to say why you want to remove that?
>
> I personally like to not set CONFIG_KMOD because the auto loader
> tends to load way too many modules. e.g. currently when someone requests
> aes on x86 you get three different aes modules (including VIA PadLock
> aes and an unoptimized C version), and keeping those around
> is just a waste.

Well, if you're building your own kernel anyway, don't build modules you don't 
want.

> Also if I didn't load a driver I prefer if it's not loaded at all.
> This is also useful for power saving for example where it's better
> to keep modules not loaded that you don't need and it's hard to
> control who accesses the respective devices.
>
> Please keep the option.

"echo /bin/true > /proc/sys/kernel/modprobe".

Given that, I don't think the config option is useful any more.

Rusty.