unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: DJ Delorie <dj@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH v2 0/3] System-wide tunables
Date: Fri, 19 Apr 2024 09:41:43 +0100	[thread overview]
Message-ID: <ZiIuRxrjPoPa7jlW@arm.com> (raw)
In-Reply-To: <xnedb22etb.fsf@greed.delorie.com>

The 04/18/2024 23:48, DJ Delorie wrote:
> This patch series is the initial implementation of system-wide
> tunables, which I mentioned a few months ago.
> 
> The first part has ldconfig read tunable information from
> /etc/tunables.conf and store it to /etc/ld.so.cache.  Reusing ldconfig
> means no new documentation or training would be required of sysadmins,
> or reprogramming of distro packaging.

a user may want multiple glibcs with different abi
on the same system (32bit, ilp32, lp64, l64p128, ..)
all sharing the same /etc/ld.so.cache (iirc this is
possible now)

tunables can differ across targets, so they need to
be checked not to cause trouble (e.g. doing a hwcap
mask specified by an int instead of arch feature can
do different things across abis)

and i'm not sure it's a good idea that one glibc cannot
be independently updated from others since tunables are
not abi stable, while iirc the /etc/ld.so.chace is
backward compat.

  reply	other threads:[~2024-04-19  8:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19  3:48 [PATCH v2 0/3] System-wide tunables DJ Delorie
2024-04-19  8:41 ` Szabolcs Nagy [this message]
2024-04-19 21:11   ` DJ Delorie
2024-04-22  8:47     ` Szabolcs Nagy

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZiIuRxrjPoPa7jlW@arm.com \
    --to=szabolcs.nagy@arm.com \
    --cc=dj@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).