On 6/23/05, Jim Cromie <jcromie@xxxxxxxxxx> wrote:
> Jim Cromie wrote:
>
> >
> >
> that wasnt supposd to go quite so soon, sorry.
> (resuming)
>
> is module initialization serialized ?
> ie various resource use race conditions precluded ?
> or is it something to watch carefully for ?
>
> and (not quite the same question)
>
> assuming C depends on B depends on A, and user modprobes C.
>
> does C start loading, to discover it needs B, then A,
> or is that sorted out before any loading starts, and its done strictly
> A,B, C ?
there exist one module dependecy file which actually defines the
dependencies between modules, mode prob uses this file to read the
dependency information and load the required modules before loading
the actual module.
you can find the dependency file in your filesystem at :
/lib/modules/2.4.18-27.7.x/modules.dep
the format of this files is something like this:
/lib/modules/2.4.18-27.7.x/kernel/drivers/char/joystick/interact.o:
/lib/modules/2.4.18-27.7.x/kernel/drivers/input/input.o \
/lib/modules/2.4.18-27.7.x/kernel/drivers/char/joystick/gameport.o
this means that module interact.o depends upon module input.o and
gameport.o, now these two module can further depend upon other
modules, which mode prob finds by iterating the module.dep file number
of times ....... the rules are something like make dependecy rules.
regards,
-Gaurav
>
> ie is the recursive made iterative ?
>
> --
> Kernelnewbies: Help each other learn about the Linux kernel.
> Archive: http://mail.nl.linux.org/kernelnewbies/
> FAQ: http://kernelnewbies.org/faq/
>
>
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
