From: 虞陆铭 <luming.yu@shingroup.cn>
To: 虞陆铭 <luming.yu@shingroup.cn>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
mpe <mpe@ellerman.id.au>, npiggin <npiggin@gmail.com>,
"christophe.leroy" <christophe.leroy@csgroup.eu>
Subject: Re:[PATCH 2/2] powerpc/locking: enable HAVE_CMPXCHG_LOCAL in kconfig
Date: Thu, 22 Aug 2024 16:31:09 +0800 [thread overview]
Message-ID: <tencent_0161BE863378EC161A2CF685@qq.com> (raw)
In-Reply-To: <4250629DA95C6D4F+20231204022303.528-2-luming.yu@shingroup.cn>
(in text)
Hi,
specific for local cmpxchg enabled on p8 powernv platform on which the patch enabled vm_state update path,
ftrace data below indicates it is at the level ofabout 4us or 5us latency, for such a big cache cold operations.
<...>-277787 [008] ..... 88366.233643: refresh_cpu_vm_stats <-vmstat_update
<idle>-0 [008] d.... 88366.233648: tick_nohz_idle_stop_tick <-do_idle
I have no diff data against the latency without the patch. But based on the estimation of the pipeline overhead for
such a big operation incurred by the vm stats update, it looks not bad.
I will do more testing and collect more histogram for different scenarios to ensure that
the latency level of understanding is something statistically make sense.
Just for the record that the small patch works as expected. :-)
BR
Luming
------------------ Original ------------------
From: "虞陆铭"<luming.yu@shingroup.cn>;
Date: Mon, Dec 4, 2023 10:23 AM
To: "linuxppc-dev"<linuxppc-dev@lists.ozlabs.org>; "linux-kernel"<linux-kernel@vger.kernel.org>; "mpe"<mpe@ellerman.id.au>; "npiggin"<npiggin@gmail.com>; "christophe.leroy"<christophe.leroy@csgroup.eu>;
Cc: "luming.yu"<luming.yu@gmail.com>; "ke.zhao"<ke.zhao@shingroup.cn>; "dawei.li"<dawei.li@shingroup.cn>; "shenghui.qu"<shenghui.qu@shingroup.cn>; "虞陆铭"<luming.yu@shingroup.cn>;
Subject: [PATCH 2/2] powerpc/locking: enable HAVE_CMPXCHG_LOCAL in kconfig
enable arch feature HAVE_CMPXCHG_LOCAL for ppc by default
Signed-off-by: Luming Yu <luming.yu@shingroup.cn>
---
arch/powerpc/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
index 6f105ee4f3cf..c10229c0243c 100644
--- a/arch/powerpc/Kconfig
+++ b/arch/powerpc/Kconfig
@@ -226,6 +226,7 @@ config PPC
select HAVE_ARCH_SECCOMP_FILTER
select HAVE_ARCH_TRACEHOOK
select HAVE_ASM_MODVERSIONS
+ select HAVE_CMPXCHG_LOCAL
select HAVE_CONTEXT_TRACKING_USER
select HAVE_C_RECORDMCOUNT
select HAVE_DEBUG_KMEMLEAK
--
2.42.0.windows.2
prev parent reply other threads:[~2024-08-22 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231204022303.528-1-luming.yu@shingroup.cn>
2023-12-04 2:23 ` [PATCH 2/2] powerpc/locking: enable HAVE_CMPXCHG_LOCAL in kconfig Luming Yu
2024-08-22 8:26 ` 虞陆铭
2024-08-22 8:31 ` 虞陆铭 [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=tencent_0161BE863378EC161A2CF685@qq.com \
--to=luming.yu@shingroup.cn \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@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 NNTP newsgroup(s).