devfs
[Top] [All Lists]

Re: module loading

To: Borzenkov Andrey <Andrey.Borzenkov@xxxxxxxxxxx>, devfs@xxxxxxxxxxx
Subject: Re: module loading
From: Russell Coker <russell@xxxxxxxxxxxx>
Date: Fri, 28 Mar 2003 14:35:18 +0100
In-reply-to: <6134254DE87BD411908B00A0C99B044F03A0B696@xxxxxxxxxxxxxxxxxxxxxxx>
References: <6134254DE87BD411908B00A0C99B044F03A0B696@xxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: Russell Coker <russell@xxxxxxxxxxxx>
Sender: devfs-bounce@xxxxxxxxxxx
User-agent: KMail/1.5.1
On Fri, 28 Mar 2003 07:50, Borzenkov Andrey wrote:
> > I would like to have the kernel run modprobe in both instances to remove
> > the
> > need for devfsd on small systems.
>
> Yes, I understand.
>
> O.K. look in fs/devfs/base.c:try_modload(). This is the function that is
> called when lookup fails. Now you could instead of calling
> devsd_notify_de() generate (relative) path using devfs_generate_path() and
> directly call modprobe.

Or perhaps I could modify devfsd_notify_de() to do this automatically when 
devfsd is not running.

> Bear in mind that devfs_generate_path() won't return absolute pathname
> (i.e. /dev/ppp) - only relative to mount point (i.e. ppp). The reason is,

Yes, that's fine.

> OTOH is overhead of running devfsd really significant? Program itself is
> pretty small and mostly sleeps.

The Familiar people working on iPaQ support seem to think that it is 
significant, which is why they don't have devfsd installed.  So for /dev/ppp 
they create the device node with mknod to allow old-style module 
auto-loading, which results in an error -17 when the module is loaded (can't 
add directory entry).

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page


<Prev in Thread] Current Thread [Next in Thread>