From: "Ludovic Courtès" <ludo@gnu.org>
To: Sergey Bugaev <bugaevc@gmail.com>
Cc: Florian Weimer <fweimer@redhat.com>,
"Carlos O'Donell" <carlos@redhat.com>,
bug-hurd@gnu.org, libc-alpha@sourceware.org
Subject: Re: [RFC PATCH 0/2] On ldconfig and ld.so.cache
Date: Wed, 24 May 2023 16:09:06 +0200 [thread overview]
Message-ID: <87sfbllt31.fsf@gnu.org> (raw)
In-Reply-To: <CAN9u=HfSgjF7U6MHZJ8nFsxZgXza3rd1RpUf5+j-0vzku8swOA@mail.gmail.com> (Sergey Bugaev's message of "Fri, 19 May 2023 16:21:53 +0300")
Hi,
Sergey Bugaev <bugaevc@gmail.com> skribis:
> On Fri, May 19, 2023 at 2:52 PM Carlos O'Donell <carlos@redhat.com> wrote:
>> Removing configuration options and making it simple to configure and use glibc is great
>> goal. I think that ldconfig should always be enabled and I don't see a downside to making
>> `use_ldconfig=yes` the default, but I think we'd have to check with Guix or Nix to see if
>> they have any custom changes there. It involves probably a slightly broader distro
>> discussion.
I missed the beginning of the discussion and I fear I’m slightly
changing topics :-), but to me we should work toward per-application
loader caches:
https://guix.gnu.org/en/blog/2021/taming-the-stat-storm-with-a-loader-cache/
https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/patches/glibc-dl-cache.patch?id=6d0571215d661d21cac2150ca45906e77a79a5fb
This is the one custom change we have in Guix.
(And IMO it should work the same on Linux and on the Hurd.)
Ludo’.
prev parent reply other threads:[~2023-05-24 14:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 18:54 Sergey Bugaev
2023-05-17 18:54 ` [RFC PATCH 1/2] elf: Port ldconfig away from stack-allocated paths Sergey Bugaev
2023-05-18 19:13 ` Adhemerval Zanella Netto
2023-05-19 12:25 ` Florian Weimer
2023-05-20 19:03 ` Sergey Bugaev
2023-05-23 17:57 ` Adhemerval Zanella Netto
2023-05-25 8:07 ` Florian Weimer
2023-05-17 18:54 ` [RFC PATCH 2/2] x86: Make dl-cache.h and readelflib.c not Linux-specific Sergey Bugaev
2023-05-19 11:36 ` Carlos O'Donell
2023-05-19 11:52 ` [RFC PATCH 0/2] On ldconfig and ld.so.cache Carlos O'Donell
2023-05-19 12:30 ` Florian Weimer
2023-05-19 13:21 ` Sergey Bugaev
2023-05-24 14:09 ` Ludovic Courtès [this message]
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=87sfbllt31.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-hurd@gnu.org \
--cc=bugaevc@gmail.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@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).