From: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Hushiyuan <hushiyuan@huawei.com>,
"H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: [PATCH] x86: Add thresholds for "rep movsb/stosb" to tunables
Date: Mon, 1 Jun 2020 16:56:58 -0400 [thread overview]
Message-ID: <CAEMqeSqAiz1sohdJOwmzYqvt=Att-Hcm8k=CtKwqpPuOUFsY8A@mail.gmail.com> (raw)
In-Reply-To: <87blm2wlzk.fsf@mid.deneb.enyo.de>
On Mon, Jun 1, 2020 at 4:48 PM Florian Weimer <fw@deneb.enyo.de> wrote:
>
> * H. J. Lu via Libc-alpha:
>
> > On Mon, Jun 1, 2020 at 1:15 PM H.J. Lu <hjl.tools@gmail.com> wrote:
> >>
> >> On Mon, Jun 1, 2020 at 12:38 PM Carlos O'Donell <carlos@redhat.com> wrote:
> >> >
> >> > On Mon, Jun 1, 2020 at 3:33 PM H.J. Lu <hjl.tools@gmail.com> wrote:
> >> > > Did you mean adding --list-tunables to ld.so? libc.so.6 doesn't take
> >> > > any arguments.
> >> >
> >> > Yes, I mean adding argument processing to libc.so.6, and handling
> >> > --list-tunables.
> >> >
> >> > We have enough infrastructure in place that wiring that up shouldn't be too bad?
> >> >
> >> > Then, even in trimmed down containers, you can just run
> >> > /lib64/libc.so.6 --list-tunables and get back the list of tunables and
> >> > their min, max, and security values.
> >>
> >> Adding an argument to libc.so.6 is difficult since argument passing is
> >> processor specific. Adding --list-tunables to ld.so? is more doable.
> >
> > But tunables are in libc.so.
>
> If this is really a problem, we can load libc.so and call a
> GLIBC_PRIVATE function to print the information.
Agreed.
Please keep in mind the original problem we are trying to solve.
We want a tunable for a parameter that is difficult to explain to the user.
To make it easier for our users to use the tunable we are going to
provide them a way to look at the tunable settings in detail.
Yes, it requires a target system, but we can't avoid that in some cases.
Cheers,
Carlos.
next prev parent reply other threads:[~2020-06-01 20:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 7:30 pthread_cond performence Discussion liqingqing
2020-03-18 12:12 ` Carlos O'Donell via Libc-alpha
2020-03-18 12:53 ` Torvald Riegel via Libc-alpha
2020-03-18 14:42 ` Carlos O'Donell via Libc-alpha
2020-05-23 4:04 ` liqingqing
2020-05-23 4:10 ` [PATCH]x86: update REP_STOSB_THRESHOLD's default value from 2k to 1M liqingqing
2020-05-23 4:37 ` [PATCH] x86: Add thresholds for "rep movsb/stosb" to tunables H.J. Lu via Libc-alpha
2020-05-28 11:56 ` H.J. Lu via Libc-alpha
2020-05-28 13:47 ` liqingqing
2020-05-29 13:13 ` Carlos O'Donell via Libc-alpha
2020-05-29 13:21 ` H.J. Lu via Libc-alpha
2020-05-29 16:18 ` Carlos O'Donell via Libc-alpha
2020-06-01 19:32 ` H.J. Lu via Libc-alpha
2020-06-01 19:38 ` Carlos O'Donell via Libc-alpha
2020-06-01 20:15 ` H.J. Lu via Libc-alpha
2020-06-01 20:19 ` H.J. Lu via Libc-alpha
2020-06-01 20:48 ` Florian Weimer
2020-06-01 20:56 ` Carlos O'Donell via Libc-alpha [this message]
2020-06-01 21:13 ` H.J. Lu via Libc-alpha
2020-06-01 22:43 ` H.J. Lu via Libc-alpha
2020-06-02 2:08 ` Carlos O'Donell via Libc-alpha
2020-06-04 21:00 ` [PATCH] libc.so: Add --list-tunables H.J. Lu via Libc-alpha
2020-06-05 22:45 ` V2 " H.J. Lu via Libc-alpha
2020-06-06 21:51 ` V3 [PATCH] libc.so: Add --list-tunables support to __libc_main H.J. Lu via Libc-alpha
2020-07-02 18:00 ` Carlos O'Donell via Libc-alpha
2020-07-02 19:08 ` [PATCH] Update tunable min/max values H.J. Lu via Libc-alpha
2020-07-03 16:14 ` Carlos O'Donell via Libc-alpha
2020-07-03 16:54 ` [PATCH] x86: Add thresholds for "rep movsb/stosb" to tunables H.J. Lu via Libc-alpha
2020-07-03 17:43 ` Carlos O'Donell via Libc-alpha
2020-07-03 17:53 ` H.J. Lu via Libc-alpha
2020-12-21 4:38 ` [PATCH]x86: update REP_STOSB_THRESHOLD's default value from 2k to 1M Siddhesh Poyarekar
2020-12-22 1:02 ` Qingqing Li
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='CAEMqeSqAiz1sohdJOwmzYqvt=Att-Hcm8k=CtKwqpPuOUFsY8A@mail.gmail.com' \
--to=libc-alpha@sourceware.org \
--cc=carlos@redhat.com \
--cc=fw@deneb.enyo.de \
--cc=hushiyuan@huawei.com \
/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).