From: Wei Xu <weixugc@google.com>
To: Jagdish Gediya <jvgediya@linux.ibm.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, baolin.wang@linux.alibaba.com,
dave.hansen@linux.intel.com, ying.huang@intel.com,
aneesh.kumar@linux.ibm.com, shy828301@gmail.com,
gthelen@google.com, dan.j.williams@intel.com
Subject: Re: [PATCH v3 2/7] mm: demotion: Add new node state N_DEMOTION_TARGETS
Date: Fri, 22 Apr 2022 13:29:22 -0700 [thread overview]
Message-ID: <CAAPL-u-LEwVpgx-c_G-tVWsGR+g3vpc=v-jD2OF9_EL5Kpq1nA@mail.gmail.com> (raw)
In-Reply-To: <20220422195516.10769-3-jvgediya@linux.ibm.com>
On Fri, Apr 22, 2022 at 12:55 PM Jagdish Gediya <jvgediya@linux.ibm.com> wrote:
>
> Some systems(e.g. PowerVM) have DRAM(fast memory) only NUMA node
> which are N_MEMORY as well as slow memory(persistent memory) only
> NUMA node which are also N_MEMORY. As the current demotion target
> finding algorithm works based on N_MEMORY and best distance, it can
> choose DRAM only NUMA node as demotion target instead of persistent
> memory node on such systems. If DRAM only NUMA node is filled with
> demoted pages then at some point new allocations can start falling
> to persistent memory, so basically cold pages are in fast memory
> (due to demotion) and new pages are in slow memory, this is why
> persistent memory nodes should be utilized for demotion and dram node
> should be avoided for demotion so that they can be used for new
> allocations.
>
> Add new state N_DEMOTION_TARGETS, node_states[N_DEMOTION_TARGETS]
> then can be used to hold the list of nodes which can be used
> as demotion targets, later patches in the series builds demotion
> targets based on nodes available in node_states[N_DEMOTION_TARGETS].
>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
> Signed-off-by: Jagdish Gediya <jvgediya@linux.ibm.com>
> ---
> drivers/base/node.c | 4 ++++
> include/linux/nodemask.h | 1 +
> 2 files changed, 5 insertions(+)
>
Acked-by: Wei Xu <weixugc@google.com>
> diff --git a/drivers/base/node.c b/drivers/base/node.c
> index ec8bb24a5a22..6eef22e6413e 100644
> --- a/drivers/base/node.c
> +++ b/drivers/base/node.c
> @@ -1038,6 +1038,9 @@ static struct node_attr node_state_attr[] = {
> [N_CPU] = _NODE_ATTR(has_cpu, N_CPU),
> [N_GENERIC_INITIATOR] = _NODE_ATTR(has_generic_initiator,
> N_GENERIC_INITIATOR),
> + [N_DEMOTION_TARGETS] = _NODE_ATTR(demotion_targets,
> + N_DEMOTION_TARGETS),
> +
> };
>
> static struct attribute *node_state_attrs[] = {
> @@ -1050,6 +1053,7 @@ static struct attribute *node_state_attrs[] = {
> &node_state_attr[N_MEMORY].attr.attr,
> &node_state_attr[N_CPU].attr.attr,
> &node_state_attr[N_GENERIC_INITIATOR].attr.attr,
> + &node_state_attr[N_DEMOTION_TARGETS].attr.attr,
> NULL
> };
>
> diff --git a/include/linux/nodemask.h b/include/linux/nodemask.h
> index 567c3ddba2c4..17844300fd57 100644
> --- a/include/linux/nodemask.h
> +++ b/include/linux/nodemask.h
> @@ -400,6 +400,7 @@ enum node_states {
> N_MEMORY, /* The node has memory(regular, high, movable) */
> N_CPU, /* The node has one or more cpus */
> N_GENERIC_INITIATOR, /* The node has one or more Generic Initiators */
> + N_DEMOTION_TARGETS, /* Nodes that should be considered as demotion targets */
> NR_NODE_STATES
> };
>
> --
> 2.35.1
>
next prev parent reply other threads:[~2022-04-22 20:29 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 19:55 [PATCH v3 0/7] mm: demotion: Introduce new node state N_DEMOTION_TARGETS Jagdish Gediya
2022-04-22 19:55 ` [PATCH v3 1/7] mm: demotion: Fix demotion targets sharing among sources Jagdish Gediya
2022-04-24 3:25 ` ying.huang
2022-04-25 9:32 ` Jagdish Gediya
2022-04-26 7:26 ` ying.huang
2022-04-22 19:55 ` [PATCH v3 2/7] mm: demotion: Add new node state N_DEMOTION_TARGETS Jagdish Gediya
2022-04-22 20:29 ` Wei Xu [this message]
2022-04-22 19:55 ` [PATCH v3 3/7] drivers/base/node: Add support to write node_states[] via sysfs Jagdish Gediya
2022-04-22 20:32 ` Wei Xu
2022-04-24 6:25 ` Aneesh Kumar K.V
2022-04-25 9:42 ` Jagdish Gediya
2022-04-24 6:29 ` ying.huang
2022-04-22 19:55 ` [PATCH v3 4/7] device-dax/kmem: Set node state as N_DEMOTION_TARGETS Jagdish Gediya
2022-04-22 20:34 ` Wei Xu
2022-04-22 19:55 ` [PATCH v3 5/7] mm: demotion: Build demotion list based on N_DEMOTION_TARGETS Jagdish Gediya
2022-04-22 20:39 ` Wei Xu
2022-04-22 19:55 ` [PATCH v3 6/7] mm: demotion: expose per-node demotion targets via sysfs Jagdish Gediya
2022-04-22 20:47 ` Wei Xu
2022-04-23 7:30 ` kernel test robot
2022-04-23 8:38 ` kernel test robot
2022-04-22 19:55 ` [PATCH v3 7/7] docs: numa: Add documentation for demotion Jagdish Gediya
2022-04-24 3:19 ` [PATCH v3 0/7] mm: demotion: Introduce new node state N_DEMOTION_TARGETS ying.huang
2022-04-25 11:15 ` Jagdish Gediya
2022-04-25 13:57 ` Jonathan Cameron
2022-04-25 14:44 ` Aneesh Kumar K V
2022-04-26 10:43 ` Jonathan Cameron
2022-04-27 1:29 ` ying.huang
2022-04-27 2:57 ` Aneesh Kumar K V
2022-04-27 3:34 ` ying.huang
2022-04-25 14:53 ` Aneesh Kumar K V
2022-04-26 10:37 ` Jonathan Cameron
2022-04-26 7:55 ` ying.huang
2022-04-26 9:07 ` Aneesh Kumar K V
2022-04-26 9:10 ` ying.huang
2022-04-26 9:37 ` Jagdish Gediya
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='CAAPL-u-LEwVpgx-c_G-tVWsGR+g3vpc=v-jD2OF9_EL5Kpq1nA@mail.gmail.com' \
--to=weixugc@google.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=gthelen@google.com \
--cc=jvgediya@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.com \
--cc=ying.huang@intel.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).