lkml.org 
[lkml]   [2002]   [Mar]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Iner Module Communications
Date

On Wednesday 13 March 2002 11:23, Robert Love wrote:

> You can call functions and touch data in other functions ... the kernel
> image, even with modules, is one big flat monolithic model.
>
> You will probably want to EXPORT_SYMBOL the functions and variables you
> want to touch ... see other modules. But basically you can access
> anything that is exported once your module is linked.
>
> Carefully consider _why_ you need "inter-module communication",
> though... and design to those (hopefully proper) goals.
>
> Robert Love


Thanks Robert.
Actually i'm trying to segregate IP and ICMP from the linux stack.
Thogh i do insmod of IP as well as ICMP, i'm having the linux stack as well.
In this case, if i do EXPORT_SYMBOL,
the LKM ICMP module can refer the IP module instead of refering LKM IP
module. But i want the LKM ICMP communicate to LKM IP only, not the kernel's
IP.

Is EXPORT_SYMBOL the only way to solve this ? Any other idea ?

Thanks,
Vinolin.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:24    [W:0.045 / U:0.040 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site