From: Janghyuck Kim <janghyuck.kim@samsung.com>
Cc: janghyuck.kim@samsung.com,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Palmer Dabbelt <palmerdabbelt@google.com>,
Atish Patra <atish.patra@wdc.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Zhengyuan Liu <liuzhengyuan@tj.kylinos.cn>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH 2/2] arm64: numa: support numa_off_fastpath
Date: Wed, 16 Jun 2021 17:37:42 +0900 [thread overview]
Message-ID: <20210616083745.14288-2-janghyuck.kim@samsung.com> (raw)
In-Reply-To: <20210616083745.14288-1-janghyuck.kim@samsung.com>
NUMA can be disabled forcefully by command line, or no configurations
are provided. numa_off_fastpath can become true in this case to skip the
memory policy related process to reduce overhead.
Signed-off-by: Janghyuck Kim <janghyuck.kim@samsung.com>
---
arch/arm64/include/asm/numa.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/include/asm/numa.h b/arch/arm64/include/asm/numa.h
index 8c8cf4297cc3..f7d4e0cb801b 100644
--- a/arch/arm64/include/asm/numa.h
+++ b/arch/arm64/include/asm/numa.h
@@ -5,4 +5,8 @@
#include <asm/topology.h>
#include <asm-generic/numa.h>
+#ifdef CONFIG_NUMA
+#define numa_off_fastpath() numa_off
+#endif /* CONFIG_NUMA */
+
#endif /* __ASM_NUMA_H */
--
2.28.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-06-16 8:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210616081628epcas2p3f919d10029cbe01efa1212a5b861af38@epcas2p3.samsung.com>
2021-06-16 8:37 ` [PATCH 1/2] mm: support fastpath if NUMA is enabled with numa off Janghyuck Kim
[not found] ` <CGME20210616081632epcas2p46436c362f3d97c9c1fb09dbb11d64ad7@epcas2p4.samsung.com>
2021-06-16 8:37 ` Janghyuck Kim [this message]
2021-06-16 17:10 ` Vlastimil Babka
2021-06-17 11:42 ` Janghyuck Kim
2021-06-16 17:32 ` Matthew Wilcox
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:
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=20210616083745.14288-2-janghyuck.kim@samsung.com \
--to=janghyuck.kim@samsung.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=atish.patra@wdc.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuzhengyuan@tj.kylinos.cn \
--cc=palmerdabbelt@google.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).