From: Sajan Karumanchi <sajan.karumanchi@gmail.com>
To: hjl.tools@gmail.com
Cc: libc-alpha@sourceware.org, carlos@redhat.com,
premachandra.mallappa@amd.com,
Sajan Karumanchi <sajan.karumanchi@amd.com>
Subject: Re: [PATCH 1/1] x86: Tuning NT Threshold parameter for AMD machines.
Date: Tue, 8 Sep 2020 17:06:38 +0530 [thread overview]
Message-ID: <20200908113638.6961-1-sajan.karumanchi@amd.com> (raw)
In-Reply-To: <CAMe9rOps7kfcZQY4jER6Y24U3vt5CesFa97La7HyTW98aTrqvA@mail.gmail.com>
Thanks H.J.Lu for reviewing the patch.
Before pushing a rebased patch, I am looking for answers regarding
the performance drop observed only in large bench variant results for
size ranges of 1MB to 8MB.
For more details, please refer to the cover letter
https://sourceware.org/pipermail/libc-alpha/2020-August/117080.html
next prev parent reply other threads:[~2020-09-08 11:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 10:45 [PATCH 0/1] " Sajan Karumanchi
2020-08-19 10:45 ` [PATCH 1/1] " Sajan Karumanchi
2020-09-01 19:23 ` H.J. Lu
2020-09-08 11:36 ` Sajan Karumanchi [this message]
2020-12-07 14:23 ` H.J. Lu
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=20200908113638.6961-1-sajan.karumanchi@amd.com \
--to=sajan.karumanchi@gmail.com \
--cc=carlos@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=premachandra.mallappa@amd.com \
--cc=sajan.karumanchi@amd.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).