From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org, Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH 0/2] Make tunable a default feature
Date: Tue, 14 Mar 2023 14:02:16 -0400 [thread overview]
Message-ID: <6511a415-b165-586d-b22d-80ff4eef0fa8@gotplt.org> (raw)
In-Reply-To: <20230313190627.2000578-1-adhemerval.zanella@linaro.org>
On 2023-03-13 15:06, Adhemerval Zanella wrote:
> It is enabled as default since 2.26, some features option require it
> (such as hwcap mask, huge pages support, and lock elisition tuning),
> and assuming its support also simplifies the build permutation.
from a historical perspective, there was not just the question of
enabling tunables but also providing multiple ways to read tunables,
each having its own parser. That is why there's a 'valstring' as an
option for --enable-tunables.
Over the years there haven't really been any other ideas to read
tunables. There's the idea of systemwide tunables through, e.g.
ld.so.conf that we'd like to have at some point, but that is more
effective alongside valstring than as an either-or feature.
There's also conceivably a use case for having only systemwide tunables
without any valstring override but maybe that should get supported when
it's actually needed by someone. So in summary, I'm not aware of
anybody using --disable-tunables, so I'm not opposed to removing the
configure flag altogether and simplifying the code. Hopefully if
someone is using it they'll come forward before this patchset gets accepted.
Thanks,
Sid
next prev parent reply other threads:[~2023-03-14 18:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 19:06 Adhemerval Zanella
2023-03-13 19:06 ` [PATCH 1/2] elf: Remove glibc.rtld.dynamic_sort tunable Adhemerval Zanella
2023-03-22 17:08 ` Siddhesh Poyarekar
2023-03-22 17:51 ` Adhemerval Zanella Netto
2023-03-22 18:40 ` Siddhesh Poyarekar
2023-03-22 18:46 ` Adhemerval Zanella Netto
2023-03-22 18:52 ` Siddhesh Poyarekar
2023-03-22 19:11 ` Adhemerval Zanella Netto
2023-03-13 19:06 ` [PATCH 2/2] Remove --enable-tunables configure option Adhemerval Zanella
2023-03-22 16:25 ` Siddhesh Poyarekar
2023-03-14 18:02 ` Siddhesh Poyarekar [this message]
2023-03-15 20:05 ` [PATCH 0/2] Make tunable a default feature Adhemerval Zanella Netto
2023-03-17 11:15 ` Siddhesh Poyarekar
2023-03-20 16:59 ` Adhemerval Zanella Netto
2023-03-20 23:15 ` Siddhesh Poyarekar
2023-03-22 14:40 ` Adhemerval Zanella Netto
2023-03-22 15:21 ` Siddhesh Poyarekar
2023-03-22 17:58 ` Adhemerval Zanella Netto
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=6511a415-b165-586d-b22d-80ff4eef0fa8@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=adhemerval.zanella@linaro.org \
--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).