[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220413092206.73974-5-jvgediya@linux.ibm.com>
Date: Wed, 13 Apr 2022 14:52:05 +0530
From: Jagdish Gediya <jvgediya@...ux.ibm.com>
To: linux-mm@...ck.org, linux-kernel@...r.kernel.org
Cc: akpm@...ux-foundation.org, aneesh.kumar@...ux.ibm.com,
baolin.wang@...ux.alibaba.com, dave.hansen@...ux.intel.com,
ying.huang@...el.com, Jagdish Gediya <jvgediya@...ux.ibm.com>
Subject: [PATCH v2 4/5] device-dax/kmem: Set node state as N_DEMOTION_TARGETS
Set dax-device node as N_DEMOTION_TARGETS so that it
can be used as demotion target.
In future, support should be added to distinguish the
dax-devices which are not preferred as demotion target
e.g. HBM, for such devices, node shouldn't be set to
N_DEMOTION_TARGETS.
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@...ux.ibm.com>
Signed-off-by: Jagdish Gediya <jvgediya@...ux.ibm.com>
---
drivers/dax/kmem.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/dax/kmem.c b/drivers/dax/kmem.c
index a37622060fff..f42ab9d04bdf 100644
--- a/drivers/dax/kmem.c
+++ b/drivers/dax/kmem.c
@@ -147,6 +147,8 @@ static int dev_dax_kmem_probe(struct dev_dax *dev_dax)
dev_set_drvdata(dev, data);
+ node_set_state(numa_node, N_DEMOTION_TARGETS);
+
return 0;
err_request_mem:
--
2.35.1
Powered by blists - more mailing lists