mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	"David S. Miller" <davem@davemloft.net>,
	Miklos Szeredi <miklos@szeredi.hu>,
	Chris Mason <chris.mason@oracle.com>,
	Alasdair G Kergon <agk@redhat.com>,
	Tigran Aivazian <tigran@aivazian.fsnet.co.uk>,
	Ian Kent <raven@themaw.net>
Subject: Re: add devname module aliases to allow module on-demand auto-loading
Date: Fri, 21 May 2010 12:34:49 +0100	[thread overview]
Message-ID: <20100521113449.GM3991@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <1274371640.302.5.camel@yio.site>

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


  parent reply	other threads:[~2010-05-21 11:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20 16:07 Kay Sievers
2010-05-21 11:11 ` Ian Kent
2010-05-21 11:24   ` Kay Sievers
2010-05-21 15:15     ` Greg KH
2010-05-21 11:34 ` Alasdair G Kergon [this message]
2010-05-21 11:51   ` Kay Sievers
2010-05-21 13:11     ` Kay Sievers
2010-05-21 13:39       ` Nikanth Karthikesan
2010-05-21 13:55         ` Kay Sievers
2010-05-21 18:23           ` Alasdair G Kergon
2010-05-21 18:51             ` Kay Sievers
2010-05-21 19:32               ` [dm-devel] " Alasdair G Kergon
2010-05-21 20:20                 ` Kay Sievers
2010-05-25  5:33               ` Luca Berra
2010-05-25  9:48                 ` Alasdair G Kergon
2010-05-25  9:57                   ` Kay Sievers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100521113449.GM3991@agk-dp.fab.redhat.com \
    --to=agk@redhat.com \
    --cc=chris.mason@oracle.com \
    --cc=davem@davemloft.net \
    --cc=gregkh@suse.de \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=raven@themaw.net \
    --cc=tigran@aivazian.fsnet.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®