From: Borislav Petkov <bp@alien8.de>
To: JY Ni <jiayu.ni@linux.alibaba.com>
Cc: Luming Yu <luming.yu@gmail.com>,
wujinhua <wujinhua@linux.alibaba.com>, x86 <x86@kernel.org>,
"zelin.deng" <zelin.deng@linux.alibaba.com>,
ak <ak@linux.intel.com>, "luming.yu" <luming.yu@intel.com>,
"fan.du" <fan.du@intel.com>,
"artie.ding" <artie.ding@linux.alibaba.com>,
"tony.luck" <tony.luck@intel.com>, tglx <tglx@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
"pawan.kumar.gupta" <pawan.kumar.gupta@linux.intel.com>,
"fenghua.yu" <fenghua.yu@intel.com>, hpa <hpa@zytor.com>,
"ricardo.neri-calderon" <ricardo.neri-calderon@linux.intel.com>,
peterz <peterz@infradead.org>
Subject: Re: 回复：[PATCH] perf: optimize clear page in Intel specified model with movq instruction
Date: Sat, 16 Oct 2021 15:22:49 +0200 [thread overview]
Message-ID: <YWrSKeT+R2S/+udL@zn.tnic> (raw)
In-Reply-To: <1cac1499-6b00-3c18-b64c-a22f269a2706@linux.alibaba.com>
On Sat, Oct 16, 2021 at 08:58:32PM +0800, JY Ni wrote:
> I rebased this patch on linux-next repo and measured the time of building a
> same kernel in original/add-movq-patch version on the same intel CPX server.
...
> delta = (*build_original_time* - *build_movq_time*) / (*build_movq_time*)
>
> This set of data shows that movq-patch version has better performance than
> original version in most cases.
First of all, please do not top-post but put your answer under the
quoted text like everyone else.
Then, please explain how exactly you ran that measurement so that I can
try to reproduce it here too.
And just to make sure we're talking about the same thing: the patch in
question is this one:
https://lore.kernel.org/r/1631177151-53723-1-git-send-email-wujinhua@linux.alibaba.com
correct?
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-10-16 13:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 8:45 [PATCH] perf: optimize clear page in Intel specified model with movq instruction Jinhua Wu
2021-09-09 9:39 ` Borislav Petkov
2021-09-09 10:34 ` Luming Yu
2021-09-09 10:44 ` Borislav Petkov
2021-09-09 11:18 ` Peter Zijlstra
[not found] ` <bf6fe59d-c760-40d4-8201-4170cd90ffc3.wujinhua@linux.alibaba.com>
2021-09-09 11:07 ` 回复：[PATCH] " Borislav Petkov
2021-09-09 14:51 ` Luming Yu
[not found] ` <1cac1499-6b00-3c18-b64c-a22f269a2706@linux.alibaba.com>
2021-10-16 13:22 ` Borislav Petkov [this message]
[not found] ` <7b07f141-12f5-397d-9e45-1d507cacae84@linux.alibaba.com>
2021-10-18 12:43 ` Borislav Petkov
2021-10-18 14:44 ` Luming Yu
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=YWrSKeT+R2S/+udL@zn.tnic \
--to=bp@alien8.de \
--cc=ak@linux.intel.com \
--cc=artie.ding@linux.alibaba.com \
--cc=fan.du@intel.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=jiayu.ni@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@gmail.com \
--cc=luming.yu@intel.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=wujinhua@linux.alibaba.com \
--cc=x86@kernel.org \
--cc=zelin.deng@linux.alibaba.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 NNTP newsgroup(s).