From: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
To: "H.J. Lu" <hjl.tools@gmail.com>, liqingqing <liqingqing3@huawei.com>
Cc: Hushiyuan <hushiyuan@huawei.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: [PATCH] x86: Add thresholds for "rep movsb/stosb" to tunables
Date: Fri, 29 May 2020 09:13:03 -0400 [thread overview]
Message-ID: <d48525c0-a931-c4f3-510c-00723084a7c0@redhat.com> (raw)
In-Reply-To: <CAMe9rOoYXMdOfedtZLx=GT-nFXThzoo7Q__H4vg=2vyOufGY6A@mail.gmail.com>
On 5/23/20 12:37 AM, H.J. Lu via Libc-alpha wrote:
> There is no single threshold value which is good for all workloads.
> I don't think we should change REP_STOSB_THRESHOLD to 1MB.
> On the other hand, the fixed threshold isn't flexible. Please try this
> patch to see if you can set the threshold for your specific workload.
My request here is that the manual include a documentation of what the
minimums are for the tunable. Even an example reference of the minimum
value would be useful for the tunable e.g. On AVX512 systems this value
is X, on AVX systems this value is Y, on all other systems Z.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2020-05-29 13:13 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 [this message]
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
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=d48525c0-a931-c4f3-510c-00723084a7c0@redhat.com \
--to=libc-alpha@sourceware.org \
--cc=carlos@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=hushiyuan@huawei.com \
--cc=liqingqing3@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).