Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756290AbZCJSW2 (ORCPT ); Tue, 10 Mar 2009 14:22:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755012AbZCJSWU (ORCPT ); Tue, 10 Mar 2009 14:22:20 -0400 Received: from nf-out-0910.google.com ([64.233.182.191]:41941 "EHLO nf-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754227AbZCJSWT (ORCPT ); Tue, 10 Mar 2009 14:22:19 -0400 MIME-Version: 1.0 In-Reply-To: <1236708806.6339.4.camel@quest> References: <20090310184624.4e28d18e@hyperion.delvare> <1236707391.6339.3.camel@quest> <20090310185558.072e6fc6@hyperion.delvare> <1236708806.6339.4.camel@quest> Date: Tue, 10 Mar 2009 19:22:16 +0100 Message-ID: Subject: Re: [PATCH 00/31] Add a lot of module alias statements From: Kay Sievers To: Scott James Remnant Cc: Jean Delvare , linux-kernel@vger.kernel.org, akpm@linux-foundation.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1785 Lines: 37 On Tue, Mar 10, 2009 at 19:13, Scott James Remnant wrote: > On Tue, 2009-03-10 at 18:55 +0100, Jean Delvare wrote: >> On Tue, 10 Mar 2009 17:49:51 +0000, Scott James Remnant wrote: >> > On Tue, 2009-03-10 at 18:46 +0100, Jean Delvare wrote: >> > >> > > 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? >> > >> > With current modprobe those files are turned into a binary index that >> > can be read and processed *much* faster. >> >> What would prevent the same binary index from being generated from >> user-provided module aliases? >> > Why go to all that effort when adding the alias to the kernel is just a > one-line change, and then it shows up along with all of the other > aliases that depmod generates the existing binary index from? The problem, with a new kernel or module, we know for forever, that we have to run depmod, but this is not the case for depmod config files, and not really to manage, to require a binary index update here. But the main point is that we want to put information where it belongs: in the module itself. Just look at the crap we ship in /etc/modprobe* and you know that externally maintained configs for kernel modules just don't work. :) Thanks, Kay -- 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/