From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: "Soni L." <fakedme+libc@gmail.com>, Libc-help <libc-help@sourceware.org>
Subject: Re: inode-based dlopen caching
Date: Mon, 7 Jun 2021 18:53:57 -0300 [thread overview]
Message-ID: <62ae59a3-cada-f56c-5f34-5e0cc26ff4d4@linaro.org> (raw)
In-Reply-To: <d3044961-ff2e-ef1c-4ba1-b14ab73d2012@gmail.com>
On 05/06/2021 10:59, Soni L. via Libc-help wrote:
> Currently dlopen caching is based on filenames, it'd be nice if it was
> based on inodes to support better "re"loading (aka loading a new module
> with the same name because unloading modules with threads is never a
> good idea). This is good for stuff that deals with plugins.
>
What do you mean by 'caching' in this scenario? glibc does not maintain
a cache of loaded libraries, different than other implementation it
does try to unload the library on dlclose (there are cases where it
is not readily possible due dependency chains).
And I am not seeing how inote-bases dlopen really helps here, if inode
changes means that file was potentially changed (so you will need to
proper dclose it). I think using filenames is in fact the proper way
here, since Linux does the hard lifting of the inode cache and provide
fast file access and mmap support for shared libraries.
next prev parent reply other threads:[~2021-06-07 21:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 13:59 Soni L.
2021-06-07 21:53 ` Adhemerval Zanella [this message]
2021-06-07 22:50 ` Soni L.
2021-06-08 13:14 ` Adhemerval Zanella
2021-06-08 16:26 ` Soni L.
2021-06-08 16:51 ` Adhemerval Zanella
2021-06-08 16:56 ` Florian Weimer
2021-06-08 17:19 ` Adhemerval Zanella
2021-06-08 17:20 ` Florian Weimer
2021-06-08 18:10 ` Soni L.
2021-06-08 18:17 ` Florian Weimer
2021-06-08 19:25 ` Adhemerval Zanella
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=62ae59a3-cada-f56c-5f34-5e0cc26ff4d4@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=fakedme+libc@gmail.com \
--cc=libc-help@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).