linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Yuquan Wang <wangyuquan1236@phytium.com.cn>
Cc: jiahao.os@bytedance.com, linux-arm-kernel@lists.infradead.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 00/19] arm64 kernel text replication
Date: Tue, 23 Jan 2024 17:25:14 +0000	[thread overview]
Message-ID: <Za/2esftSXq4+aa5@shell.armlinux.org.uk> (raw)
In-Reply-To: <20240123103509.696983-1-wangyuquan1236@phytium.com.cn>

On Tue, Jan 23, 2024 at 06:35:09PM +0800, Yuquan Wang wrote:
> > 
> > After applying these patches, we tested that our business performance
> > increased by more than 5% and the NUMA node memory bandwidth was more
> > balanced.
> > 
> 
> I have successfully applied your patches on my arm64 linux. And I could 
> start it with a qemu machine(virt). However, I don't know the way to test
> the performance it brings to the kernel. Do you have some suggestions?

Please can I make one thing utterly clear... kernel text replication
in a virtual machine generally doesn't make sense unless one can
setup the virtual machine to be truly NUMA. In other words, groups
of CPUs with their local memory and remote-node memory having higher
latency.

Kernel text replication is something which solves the problem on
bare metal NUMA machines where running kernel text that is located
in a foreign node results in the CPU running slower than it would
do if the kernel text were in its local RAM.

Unless the VM is setup in exactly that way, then kernel text
replication has no place in a VM, and probably would result in
poorer performance.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2024-01-23 17:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240123103509.696983-1-wangyuquan1236@phytium.com.cn>
2024-01-23 11:32 ` [External] Re:[PATCH v3 00/19] arm64 kernel text replication Hao Jia
2024-01-23 17:25 ` Russell King (Oracle) [this message]
2024-01-17  8:53 [PATCH " Hao Jia
2024-01-17  9:41 ` Russell King (Oracle)

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=Za/2esftSXq4+aa5@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=jiahao.os@bytedance.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=wangyuquan1236@phytium.com.cn \
    /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).