From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Sajan Karumanchi <sajan.karumanchi@gmail.com>
Cc: bmerry@sarao.ac.za, goldstein.w.n@gmail.com, hjl.tools@gmail.com,
libc-alpha@sourceware.org, pmallapp@amd.com,
sajan.karumanchi@amd.com, fweimer@redhat.com
Subject: Re: [PATCH 0/4] x86: Improve ERMS usage on Zen3+
Date: Tue, 6 Feb 2024 10:00:07 -0300 [thread overview]
Message-ID: <a9596bb0-96e7-4d51-b6c2-b8d9dba2280e@linaro.org> (raw)
In-Reply-To: <20240205190108.2332109-1-sajan.karumanchi@amd.com>
On 05/02/24 16:01, Sajan Karumanchi wrote:
>
> Adhemerval,
>
> In our extensive testing, we observed mixed results for rep-movs/stos performance with the ERMS feature enabled.
> Henceforth, we approve this patch to avoid the ERMS code path on AMD processors for better performance.
>
> -Sajan
>
>
Thanks for checking this out Sajan, I will rebase with some wording fixes
in comments and double check if everything is ok. If you can, please
send a Ack-by or Reviewed-by in the next comment. I will also check with
H.J and Noah (x86 maintaners) to see if everything is ok.
prev parent reply other threads:[~2024-02-06 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 20:09 Adhemerval Zanella
2023-10-31 20:09 ` [PATCH 1/4] elf: Add a way to check if tunable is set (BZ 27069) Adhemerval Zanella
2023-10-31 20:09 ` [PATCH 2/4] x86: Fix Zen3/Zen4 ERMS selection (BZ 30994) Adhemerval Zanella
2023-10-31 20:09 ` [PATCH 3/4] x86: Do not prefer ERMS for memset on Zen3+ Adhemerval Zanella
2023-10-31 20:09 ` [PATCH 4/4] x86: Expand the comment on when REP STOSB is used on memset Adhemerval Zanella
2023-11-15 19:05 ` [PATCH 0/4] x86: Improve ERMS usage on Zen3+ sajan.karumanchi
2023-11-16 18:35 ` Adhemerval Zanella Netto
2024-02-05 19:01 ` Sajan Karumanchi
2024-02-06 13:00 ` Adhemerval Zanella Netto [this message]
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=a9596bb0-96e7-4d51-b6c2-b8d9dba2280e@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=bmerry@sarao.ac.za \
--cc=fweimer@redhat.com \
--cc=goldstein.w.n@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=pmallapp@amd.com \
--cc=sajan.karumanchi@amd.com \
--cc=sajan.karumanchi@gmail.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).