devfs
[Top] [All Lists]

RE: module loading

To: "'Russell Coker'" <russell@xxxxxxxxxxxx>, devfs@xxxxxxxxxxx
Subject: RE: module loading
From: Borzenkov Andrey <Andrey.Borzenkov@xxxxxxxxxxx>
Date: Fri, 28 Mar 2003 17:09:34 +0300
Importance: Normal
In-reply-to: <200303281435.18213.russell@xxxxxxxxxxxx>
Sender: devfs-bounce@xxxxxxxxxxx
> > 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.
> 

not without further changes. Try_modload checks event mask and does not call
devfsd_notify_de if it does not include LOOKUP. OTOH this check looks
redundant; it is repeated in devfsd_notify_de anyway.

Besides devfsd_notify_de is called in other cases as well, not just to do
modprobe. So try_modload looks more logical choice.

-andrey


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