From: Wei Liu <wei.liu@kernel.org>
To: Li RongQing <lirongqing@baidu.com>
Cc: kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, x86@kernel.org, linux-hyperv@vger.kernel.org
Subject: Re: [PATCH] x86/hyperv: Consider NUMA affinity when allocating memory for per-CPU vmsa
Date: Mon, 22 Apr 2024 22:28:57 +0000 [thread overview]
Message-ID: <ZibkqT2XMOatmkcK@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <20240415085712.49980-1-lirongqing@baidu.com>
On Mon, Apr 15, 2024 at 04:57:12PM +0800, Li RongQing wrote:
> per-CPU vmsa are dominantly accessed from their own local CPUs,
> so allocate them node-local to improve performance.
>
> And reorganized variables to be reverse christmas tree order
>
> Signed-off-by: Li RongQing <lirongqing@baidu.com>
Applied. Thanks.
prev parent reply other threads:[~2024-04-22 22:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 8:57 [PATCH] x86/hyperv: Consider NUMA affinity when allocating memory for per-CPU vmsa Li RongQing
2024-04-22 22:28 ` Wei Liu [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=ZibkqT2XMOatmkcK@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=bp@alien8.de \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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