From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Incremental Linking
Date: Wed, 23 May 2012 00:40:28 +0700 [thread overview]
Message-ID: <CAGdaadao1LV0xhbrU9_m+Nh04RBdKiosnL1P+RDp4yP++JWHjw@mail.gmail.com> (raw)
In-Reply-To: <1337680595.36648.YahooMailNeo@web161202.mail.bf1.yahoo.com>
On Tue, May 22, 2012 at 4:56 PM, somanath sahoo <bapi_mvit2004@yahoo.com> wrote:
> Hi,
>
> As newbie in linux kernel,?I would like to?understand?the concept of
> "incremental linking?" w.r.t to linux kernel module.
>
> I have read that?kernel loadable modules are?being generated and
> inserted?into a running kernel?due to this?"incremental linking "
> technology.
>
> If anyone can provide me some pointers to understand the "incremental
> linking" concept, it will be needful.
perhaps you meant lazy binding? same thing like what glibc does in
user space I believe.
In short, symbols (functions etc) are not resolved right away, but
looked up and referenced when needed only.
Hopefully I point you the correct meaning. If not, feel free to CMIIW.
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
next prev parent reply other threads:[~2012-05-22 17:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 9:56 Incremental Linking somanath sahoo
2012-05-22 15:17 ` Jonathan Neuschäfer
2012-05-23 5:39 ` somanath sahoo
[not found] ` <CAP2rAF8dY4tS3aZ_+OBnv2eNK07wMvhjoC=TEaQF8AGXgc=5vg@mail.gmail.com>
[not found] ` <1337757675.30429.YahooMailNeo@web161202.mail.bf1.yahoo.com>
2012-05-23 7:50 ` Sarbojit Ganguly
2012-05-23 7:51 ` Sarbojit Ganguly
2012-05-22 17:40 ` Mulyadi Santosa [this message]
2012-05-23 16:17 ` Dave Hylands
2012-05-23 16:51 ` Sarbojit Ganguly
2012-05-23 17:03 ` Dave Hylands
2012-05-28 7:58 ` Jim Cromie
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=CAGdaadao1LV0xhbrU9_m+Nh04RBdKiosnL1P+RDp4yP++JWHjw@mail.gmail.com \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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;
as well as URLs for NNTP newsgroup(s).