From: <tyler@agat.net>
To: linux-kernel@vger.kernel.org
Cc: gregkh@suse.de
Subject: Re: [PATCH] Kmod optimization
Date: Thu, 13 Apr 2006 21:04:12 +0200 [thread overview]
Message-ID: <20060413190412.GA30541@Starbuck> (raw)
In-Reply-To: <20060413185014.GA27130@suse.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 2068 bytes --]
On Thu, Apr 13, 2006 at 11:50:14AM -0700, Greg KH wrote:
> On Thu, Apr 13, 2006 at 08:36:17PM +0200, tyler@agat.net wrote:
> > On Thu, Apr 13, 2006 at 11:24:01AM -0700, Greg KH wrote:
> > > On Thu, Apr 13, 2006 at 08:03:45PM +0200, tyler@agat.net wrote:
> > > > Hi,
> > > >
> > > > the request_mod functions try to load automatically a module by running
> > > > a user mode process helper (modprobe).
> > > >
> > > > The user process is launched even if the module is already loaded. I
> > > > think it would be better to test if the module is already loaded.
> > >
> > > Does this cause a problem somehow? request_mod is called _very_
> > > infrequently from a normal kernel these days, so I really don't think
> > > this is necessary.
> >
> > Yes I agree it _should_ be very infrequently called but it _will_ be very
> > infrequently called just if the user space configuration is done properly.
>
> What do you mean by this? Almost all 2.6 distros use udev today, which
> prevents this code from ever getting called. So odds are, you are
> optimising something that no one will ever use :)
Well perhaps I don't understand the mechanism :) But let's take an
example.
On all kernels (even recent), if the module smbfs is loaded, it's not
handled by udev and request_module could be called.
Let"s take another example to see to illustrate why I think
it depends on the user configuration :
module A depends on module B
if we have a script which do "insmod moduleA.ko ; insmod moduleB.ko",
there will be a call to request_module.
if the script is "insmod moduleB.ko ; insmod moduleA.ko", request_mode
is not called.
I know the first script is really idiot :)
This is what I was thinking about in my previous mail.
--
tyler
tyler@agat.net
___________________________________________________________________________
Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel.
Rendez-vous sur http://fr.yahoo.com/set
next prev parent reply other threads:[~2006-04-13 19:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 18:03 [PATCH] Kmod optimization tyler
2006-04-13 18:19 ` Randy.Dunlap
2006-04-13 18:57 ` Jan Engelhardt
2006-04-13 18:24 ` Greg KH
2006-04-13 18:36 ` tyler
2006-04-13 18:50 ` Greg KH
2006-04-13 19:04 ` tyler [this message]
2006-04-13 22:53 ` Roman Zippel
2006-04-13 23:13 ` Greg KH
2006-04-14 10:57 ` tyler
2006-04-13 19:10 ` Paulo Marques
2006-04-13 19:17 ` tyler
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=20060413190412.GA30541@Starbuck \
--to=tyler@agat.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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