archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <>
To: Janghyuck Kim <>
Cc: Catalin Marinas <>,
	Will Deacon <>,
	Andrew Morton <>,
	Palmer Dabbelt <>,
	Atish Patra <>, Gavin Shan <>,
	Zhengyuan Liu <>,,,
Subject: Re: [PATCH 1/2] mm: support fastpath if NUMA is enabled with numa off
Date: Wed, 16 Jun 2021 18:32:50 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Jun 16, 2021 at 05:37:41PM +0900, Janghyuck Kim wrote:
> Architecture might support fake node when CONFIG_NUMA is enabled but any
> node settings were supported by ACPI or device tree. In this case,
> getting memory policy during memory allocation path is meaningless.
> Moreover, performance degradation was observed in the minor page fault
> test, which is provided by (
> Average faults/sec of enabling NUMA with fake node was 5~6 % worse than
> disabling NUMA. To reduce this performance regression, fastpath is
> introduced. fastpath can skip the memory policy checking if NUMA is
> enabled but it uses fake node. If architecture doesn't support fake
> node, fastpath affects nothing for memory allocation path.

This patch doesn't even apply to the current kernel, but putting that
aside, what's the expensive part of the current code?  That is,
comparing performance stats between this numa_off enabled and numa_off
disabled, where do you see taking a lot of time?

linux-arm-kernel mailing list

  parent reply	other threads:[~2021-06-16 17:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2021-06-16  8:37 ` [PATCH 1/2] mm: support fastpath if NUMA is enabled with numa off Janghyuck Kim
     [not found]   ` <>
2021-06-16  8:37     ` [PATCH 2/2] arm64: numa: support numa_off_fastpath Janghyuck Kim
2021-06-16 17:10   ` [PATCH 1/2] mm: support fastpath if NUMA is enabled with numa off Vlastimil Babka
2021-06-17 11:42     ` Janghyuck Kim
2021-06-16 17:32   ` Matthew Wilcox [this message]
2021-06-17 11:55     ` Janghyuck Kim
2021-06-17 12:40       ` Matthew Wilcox

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).