Bug#597658: Wouldn't it be better solved the /etc/modprobe.d/blacklist.conf?
On Mon, Oct 25, 2010 at 06:59:50PM +0100, Ben Hutchings wrote:
> On Fri, Oct 22, 2010 at 02:41:50PM +0200, Klaus Umbach wrote:
> > Wouldn't it be better, to put the module in /etc/modprobe.d/blacklist.conf,
> > instead of disabling it completely? So those who are able to use it, can
> > still load it and do not have to build their own kernel.
>
> blacklist.conf applies to every installed kernel version, and is actually
> owned by udev. For this reason we never blacklist modules in that way.
>
> > This module lowers the CPU usage of kcryptd from 90% to 25% on my machine,
> > when writing to disk. So it would be great to have it.
>
> What we can do is to disable auto-loading by removing the device table
> from the module. The user can then force loading at boot time by editing
> /etc/modules or /etc/initramfs-tools/modules (depending on how early the
> module should be loaded).
>
What about re-enabling this feature in experimental? This way we can see
if the problem is still present on recent kernel versions, and it's less
problematic in case the problem is still present than doing that in
squeeze.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
Reply to: