* Richard W. M. Jones: > On Wed, Sep 01, 2021 at 11:01:01AM +0200, Florian Weimer wrote: >> There are some packages that install f[ile]s into /etc/ld.so.conf.d, and >> such packages still have to run ldconfig explicitly. (We should perhaps >> move those shared objects to /usr/lib64, too.) > > Did anyone measure if ldconfig caching is actually useful on > modern machines? It's not actually a cache in the strictest sense. Shared objects installed into directories listed in /etc/ld.so.conf, /etc/ld.so.conf.d can only be loaded after running ldconfig. The dynamic loader does not parse these configuration files. On some architectures (s390x in particular), hundreds of additional system calls are needed just for loading just libc.so.6. These are all failing open calls. The kernel does not have a negative dentry cache, so I expect them to be quite slow. There are glibc plans to reduce this to a more manageable count (perhaps ~20 system calls) by removing the legacy HWCAPS mechanism, but this hasn't happened yet (the feature was deprecated in 2.33 only). Thanks, Florian _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
