From: Ying Huang <ying.huang@intel.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
linux-mm@kvack.org, akpm@linux-foundation.org
Cc: Wei Xu <weixugc@google.com>, Greg Thelen <gthelen@google.com>,
Yang Shi <shy828301@gmail.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Tim C Chen <tim.c.chen@intel.com>,
Brice Goglin <brice.goglin@gmail.com>,
Michal Hocko <mhocko@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hesham Almatary <hesham.almatary@huawei.com>,
Dave Hansen <dave.hansen@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Alistair Popple <apopple@nvidia.com>,
Dan Williams <dan.j.williams@intel.com>,
Feng Tang <feng.tang@intel.com>,
Jagdish Gediya <jvgediya@linux.ibm.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
David Rientjes <rientjes@google.com>
Subject: Re: [PATCH v6 04/13] mm/demotion/dax/kmem: Set node's memory tier to MEMORY_TIER_PMEM
Date: Mon, 13 Jun 2022 14:59:12 +0800 [thread overview]
Message-ID: <193ad45f2ec47ac157a812975f3e4235fcbc061a.camel@intel.com> (raw)
In-Reply-To: <20220610135229.182859-5-aneesh.kumar@linux.ibm.com>
On Fri, 2022-06-10 at 19:22 +0530, Aneesh Kumar K.V wrote:
> By default, all nodes are assigned to DEFAULT_MEMORY_TIER which
> is the memory tier designated for nodes with DRAM
>
> Set dax kmem device node's tier to MEMORY_TIER_PMEM. MEMORY_TIER_PMEM
> is assigned a default rank value of 100 and appears below DEFAULT_MEMORY_TIER
> in demotion order.
>
> Signed-off-by: Jagdish Gediya <jvgediya@linux.ibm.com>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
> ---
> drivers/dax/kmem.c | 4 ++
> include/linux/memory-tiers.h | 1 +
> mm/memory-tiers.c | 78 ++++++++++++++++++++++++++++++++++++
> 3 files changed, 83 insertions(+)
>
> diff --git a/drivers/dax/kmem.c b/drivers/dax/kmem.c
> index a37622060fff..0cb3de3d138f 100644
> --- a/drivers/dax/kmem.c
> +++ b/drivers/dax/kmem.c
> @@ -11,6 +11,7 @@
> #include <linux/fs.h>
> #include <linux/mm.h>
> #include <linux/mman.h>
> +#include <linux/memory-tiers.h>
> #include "dax-private.h"
> #include "bus.h"
>
>
> @@ -147,6 +148,9 @@ static int dev_dax_kmem_probe(struct dev_dax *dev_dax)
>
>
> dev_set_drvdata(dev, data);
>
>
> +#ifdef CONFIG_TIERED_MEMORY
> + node_create_and_set_memory_tier(numa_node, MEMORY_TIER_PMEM);
> +#endif
> return 0;
>
>
> err_request_mem:
> diff --git a/include/linux/memory-tiers.h b/include/linux/memory-tiers.h
> index 44c3c3b16a36..e102ec73ab80 100644
> --- a/include/linux/memory-tiers.h
> +++ b/include/linux/memory-tiers.h
> @@ -18,6 +18,7 @@
> #define MAX_MEMORY_TIERS 3
>
>
> extern bool numa_demotion_enabled;
> +int node_create_and_set_memory_tier(int node, int tier);
> #else
> #define numa_demotion_enabled false
>
>
> diff --git a/mm/memory-tiers.c b/mm/memory-tiers.c
> index c3123a457d90..00d393a5a628 100644
> --- a/mm/memory-tiers.c
> +++ b/mm/memory-tiers.c
> @@ -67,6 +67,84 @@ static struct memory_tier *register_memory_tier(unsigned int tier,
> return memtier;
> }
>
>
> +static struct memory_tier *__node_get_memory_tier(int node)
> +{
> + struct memory_tier *memtier;
> +
> + list_for_each_entry(memtier, &memory_tiers, list) {
> + if (node_isset(node, memtier->nodelist))
> + return memtier;
> + }
> + return NULL;
> +}
> +
I suggest to add NODE_DATA(nid)->mem_tier before this patch. That is,
part of [9/13]. That will make code much simpler and easier to
review.
And, in addition to dax_kmem, whenever a normal node is onlined, we
need to add it to the default memory tier. I found this is done in
[5/13]. IMHO, we should move that part before this patch.
Best Regards,
Huang, Ying
> +static struct memory_tier *__get_memory_tier_from_id(int id)
> +{
> + struct memory_tier *memtier;
> +
> + list_for_each_entry(memtier, &memory_tiers, list) {
> + if (memtier->id == id)
> + return memtier;
> + }
> + return NULL;
> +}
> +
> +static int __node_create_and_set_memory_tier(int node, int tier)
> +{
> + int ret = 0;
> + struct memory_tier *memtier;
> +
> + memtier = __get_memory_tier_from_id(tier);
> + if (!memtier) {
> + int rank;
> +
> + rank = get_rank_from_tier(tier);
> + if (rank == -1) {
> + ret = -EINVAL;
> + goto out;
> + }
> + memtier = register_memory_tier(tier, rank);
> + if (!memtier) {
> + ret = -EINVAL;
> + goto out;
> + }
> + }
> + node_set(node, memtier->nodelist);
> +out:
> + return ret;
> +}
> +
> +int node_create_and_set_memory_tier(int node, int tier)
> +{
> + struct memory_tier *current_tier;
> + int ret = 0;
> +
> + mutex_lock(&memory_tier_lock);
> +
> + current_tier = __node_get_memory_tier(node);
> + if (!current_tier) {
> + ret = __node_create_and_set_memory_tier(node, tier);
> + goto out;
> + }
> +
> + if (current_tier->id == tier)
> + goto out;
> +
> + node_clear(node, current_tier->nodelist);
> +
> + ret = __node_create_and_set_memory_tier(node, tier);
> + if (ret) {
> + /* reset it back to older tier */
> + node_set(node, current_tier->nodelist);
> + goto out;
> + }
> +out:
> + mutex_unlock(&memory_tier_lock);
> +
> + return ret;
> +}
> +EXPORT_SYMBOL_GPL(node_create_and_set_memory_tier);
> +
> static int __init memory_tier_init(void)
> {
> struct memory_tier *memtier;
next prev parent reply other threads:[~2022-06-13 6:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 13:52 [PATCH v6 00/13] mm/demotion: Memory tiers and demotion Aneesh Kumar K.V
2022-06-10 13:52 ` [PATCH v6 01/13] mm/demotion: Add support for explicit memory tiers Aneesh Kumar K.V
2022-06-13 3:22 ` Ying Huang
2022-06-13 3:31 ` Aneesh Kumar K V
2022-06-13 5:30 ` Ying Huang
2022-06-13 13:16 ` Johannes Weiner
2022-06-13 13:28 ` Aneesh Kumar K V
2022-06-14 8:20 ` Aneesh Kumar K.V
2022-06-14 15:13 ` Davidlohr Bueso
2022-06-10 13:52 ` [PATCH v6 02/13] mm/demotion: Move memory demotion related code Aneesh Kumar K.V
2022-06-10 13:52 ` [PATCH v6 03/13] mm/demotion: Return error on write to numa_demotion sysfs Aneesh Kumar K.V
2022-06-13 3:26 ` Ying Huang
2022-06-13 3:35 ` Aneesh Kumar K V
2022-06-13 5:33 ` Ying Huang
2022-06-13 5:48 ` Aneesh Kumar K V
2022-06-14 8:40 ` Ying Huang
2022-06-10 13:52 ` [PATCH v6 04/13] mm/demotion/dax/kmem: Set node's memory tier to MEMORY_TIER_PMEM Aneesh Kumar K.V
2022-06-13 6:59 ` Ying Huang [this message]
2022-06-13 7:05 ` Aneesh Kumar K V
2022-06-10 13:52 ` [PATCH v6 05/13] mm/demotion: Build demotion targets based on explicit memory tiers Aneesh Kumar K.V
2022-06-10 13:52 ` [PATCH v6 06/13] mm/demotion: Expose memory tier details via sysfs Aneesh Kumar K.V
2022-06-10 13:52 ` [PATCH v6 07/13] mm/demotion: Add per node memory tier attribute to sysfs Aneesh Kumar K.V
2022-06-10 13:52 ` [PATCH v6 08/13] mm/demotion: Add support for memory tier creation from userspace Aneesh Kumar K.V
2022-06-10 13:52 ` [PATCH v6 09/13] mm/demotion: Add pg_data_t member to track node memory tier details Aneesh Kumar K.V
2022-06-13 7:07 ` Ying Huang
2022-06-10 13:52 ` [PATCH v6 10/13] mm/demotion: Demote pages according to allocation fallback order Aneesh Kumar K.V
2022-06-10 13:52 ` [PATCH v6 11/13] mm/demotion: Update node_is_toptier to work with memory tiers Aneesh Kumar K.V
2022-06-10 13:52 ` [PATCH v6 12/13] mm/demotion: Add documentation for memory tiering Aneesh Kumar K.V
2022-06-10 13:52 ` [PATCH v6 13/13] mm/demotion: Add sysfs ABI documentation Aneesh Kumar K.V
-- strict thread matches above, loose matches on Subject: below --
2022-06-10 13:49 [PATCH v6 00/13] mm/demotion: Memory tiers and demotion Aneesh Kumar K.V
2022-06-10 13:49 ` [PATCH v6 04/13] mm/demotion/dax/kmem: Set node's memory tier to MEMORY_TIER_PMEM Aneesh Kumar K.V
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=193ad45f2ec47ac157a812975f3e4235fcbc061a.camel@intel.com \
--to=ying.huang@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=apopple@nvidia.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=brice.goglin@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave@stgolabs.net \
--cc=feng.tang@intel.com \
--cc=gthelen@google.com \
--cc=hesham.almatary@huawei.com \
--cc=jvgediya@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=rientjes@google.com \
--cc=shy828301@gmail.com \
--cc=tim.c.chen@intel.com \
--cc=weixugc@google.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