kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Lev Olshvang <levonshe@yandex.com>
To: kernelnewbies <kernelnewbies@kernelnewbies.org>,
	linux-il <linux-il@cs.huji.ac.il>
Subject: How to signal kernel that shared library is not in use by any process anymore ?
Date: Fri, 21 Dec 2018 17:20:36 +0300	[thread overview]
Message-ID: <965981545402036@sas1-2b3c3045b736.qloud-c.yandex.net> (raw)


Hi All,

I have  an executable (C++) which is the exclusive user of the some shared library that it uses only during  the initialization phase.

I would like to free memory used by this shared library, because I am running on embedded system.

How can I achieve this?

I know that dlopen() will load shared library, and hope that following dlclose() will free this lib memory. 

1. Still  I do not know what method should be used to make dynamic linker look again into executable and resolve symbols of the newly appeared symbols ?
2. And  how to tell the dynamic linker ld-linux.so to postpone the symbol resolution until dlopen()  will load  the library?
3. Whether to compile and link executable with this library or leave unresolved symbols?

Waiting for your advises,
Lev.

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

             reply	other threads:[~2018-12-21 14:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-21 14:20 Lev Olshvang [this message]
2018-12-21 15:31 ` How to signal kernel that shared library is not in use by any process anymore ? Greg KH
2018-12-27  7:47   ` Lev Olshvang
2018-12-27  9:43     ` Greg KH
2018-12-21 16:37 ` Lior Okman
2019-01-08 15:56   ` Lev Olshvang
2018-12-22  2:34 ` Bernd Petrovitsch

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=965981545402036@sas1-2b3c3045b736.qloud-c.yandex.net \
    --to=levonshe@yandex.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-il@cs.huji.ac.il \
    /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).