From: "Zack Weinberg" <zack@owlfolio.org>
To: "Adhemerval Zanella" <adhemerval.zanella@linaro.org>,
"DJ Delorie" <dj@redhat.com>
Cc: "GNU libc development" <libc-alpha@sourceware.org>
Subject: Re: RFC: system-wide default tunables
Date: Tue, 17 Oct 2023 13:40:47 -0400 [thread overview]
Message-ID: <9b118ff8-db2f-407d-858b-b526b6805467@app.fastmail.com> (raw)
In-Reply-To: <cf589d17-c71b-48bd-a500-67a6b445a082@linaro.org>
On Tue, Oct 17, 2023, at 10:10 AM, Adhemerval Zanella Netto wrote:
> On 06/10/23 17:25, DJ Delorie wrote:
>> Adhemerval Zanella Netto <adhemerval.zanella@linaro.org> writes:
>>> The hwcap-related are still used for library selection, the original
>>> intention of the ld.so.cache. What I am afraid is ld.so.cache start to
>>> being an umbrella for different and unrelated settings.
>>
>> The alternative is to add an /etc/tunables.cache which would correspond
>> to /etc/tunables.conf and/or /etc/tunables.conf.d/*
>>
>> On most systems (no files) that would add one unsuccessful stat() call.
>
> We can use 'access' to check for file existent first and then read the whole
> file, as we do for /etc/ld.so.preload. It should slight faster than stat.
Even better to open() unconditionally and ignore ENOENT failures.
zw
next prev parent reply other threads:[~2023-10-17 17:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 20:55 DJ Delorie
2023-10-06 14:44 ` Adhemerval Zanella Netto
2023-10-06 17:12 ` Adhemerval Zanella Netto
2023-10-06 18:29 ` DJ Delorie
2023-10-06 19:14 ` Adhemerval Zanella Netto
2023-10-06 20:25 ` DJ Delorie
2023-10-17 14:10 ` Adhemerval Zanella Netto
2023-10-17 14:17 ` Siddhesh Poyarekar
2023-10-17 14:37 ` Siddhesh Poyarekar
2023-10-17 15:43 ` DJ Delorie
2023-10-17 15:58 ` Siddhesh Poyarekar
2023-10-17 16:45 ` DJ Delorie
2023-10-17 16:55 ` Siddhesh Poyarekar
2023-10-17 17:14 ` DJ Delorie
2023-10-18 14:20 ` Siddhesh Poyarekar
2023-10-17 17:40 ` Zack Weinberg [this message]
2023-10-17 17:47 ` DJ Delorie
2023-10-17 18:17 ` Zack Weinberg
2023-10-17 18:21 ` DJ Delorie
2023-10-06 22:04 ` DJ Delorie
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=9b118ff8-db2f-407d-858b-b526b6805467@app.fastmail.com \
--to=zack@owlfolio.org \
--cc=adhemerval.zanella@linaro.org \
--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).