[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100521113449.GM3991@agk-dp.fab.redhat.com>
Date: Fri, 21 May 2010 12:34:49 +0100
From: Alasdair G Kergon <agk@...hat.com>
To: Kay Sievers <kay.sievers@...y.org>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...e.de>,
"David S. Miller" <davem@...emloft.net>,
Miklos Szeredi <miklos@...redi.hu>,
Chris Mason <chris.mason@...cle.com>,
Alasdair G Kergon <agk@...hat.com>,
Tigran Aivazian <tigran@...azian.fsnet.co.uk>,
Ian Kent <raven@...maw.net>
Subject: Re: add devname module aliases to allow module on-demand
auto-loading
On Thu, May 20, 2010 at 06:07:20PM +0200, Kay Sievers wrote:
> This adds:
> alias: devname:<name>
> to some common kernel modules, which will allow the on-demand loading
> of the kernel module when the device node is accessed.
I don't see any need for this for device-mapper: please leave dm out of this.
> Ideally all these modules would be compiled-in,
Why do you think that? Currently that's a matter for the user/distro to
decide! IMHO It's really not for the kernel to force a policy like this on its
users. If that's what you think, why does your patch instead not go the whole
way and refuse to allow these items even to be compiled as modules?
> but distros seems too
> much in love with their modularization that we need to cover the common
> cases with this new facility. It will allow us to remove a bunch of pretty
> useless init scripts and modprobes from init scripts.
Again, I don't see why this needs any kernel changes. If this was
important, any distro could deal with it itself trivially without needing
a kernel patch.
Nack for the dm part of this from my point of view as it removes flexibility
with a 'one size fits all' approach that introduces a fixed minor number
into a dynamic world.
Alasdair
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists