Re: Help - does module run as a single thread process?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Monday 21 June 2004 11:21, l x wrote:
> Hi,
>
> I'm working on a module and would appreciate it if
> some one could help me on this.
>
> Suppose there are two modules, modA and modB.  What's
> going to happen if modB calls a function,
> modA_func_2(), defined in modA while modA is running
> another function of its own, modA_func_1()?
>
> I need modA completes modA_func_1() before responsing
> to modB's call to modA_func_2().  Can I assume kernel
> will do this for me?  If I understand right, a module
> runs as a single thread process.  Therefore, when
> something is running, other requests must wait.
> Please correct me if I'm wrong.

A module is *not* a process.  It is not even anything even remotely 
similar to a process.  If it helps, pretend you are not using a module.



--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux