From: Robert Love <rml@tech9.net>
To: vinolin <vinolin@nodeinfotech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Iner Module Communications
Date: 13 Mar 2002 00:53:39 -0500 [thread overview]
Message-ID: <1015998820.856.1.camel@phantasy> (raw)
In-Reply-To: <02031311152001.00884@Vinolin>
In-Reply-To: <02031311152001.00884@Vinolin>
On Wed, 2002-03-13 at 00:45, vinolin wrote:
> Is it possible to perform inermodule communications between the LKM s?
> Any idea ?
> Please share with me.
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
next prev parent reply other threads:[~2002-03-13 5:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 5:45 Iner Module Communications vinolin
2002-03-13 5:53 ` Robert Love [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-13 8:52 vinolin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1015998820.856.1.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vinolin@nodeinfotech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox