From: Gregory Price <gourry.memverge@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-cxl@vger.kernel.org, linux-mm@kvack.org,
ying.huang@intel.com, akpm@linux-foundation.org,
aneesh.kumar@linux.ibm.com, weixugc@google.com,
apopple@nvidia.com, hannes@cmpxchg.org, tim.c.chen@intel.com,
dave.hansen@intel.com, mhocko@kernel.org, shy828301@gmail.com,
gregkh@linuxfoundation.org, rafael@kernel.org,
Gregory Price <gregory.price@memverge.com>
Subject: [RFC PATCH v3 2/4] node: add accessors to sysfs when nodes are created
Date: Mon, 30 Oct 2023 20:38:08 -0400 [thread overview]
Message-ID: <20231031003810.4532-3-gregory.price@memverge.com> (raw)
In-Reply-To: <20231031003810.4532-1-gregory.price@memverge.com>
Accessor information is presently only exposed when hmat information
is registered. Add accessor information at node creation to allow
new attributes to be added even in the absense of hmat information.
Signed-off-by: Gregory Price <gregory.price@memverge.com>
---
drivers/base/node.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/drivers/base/node.c b/drivers/base/node.c
index 4d588f4658c8..b09c9c8e6830 100644
--- a/drivers/base/node.c
+++ b/drivers/base/node.c
@@ -868,7 +868,9 @@ int __register_one_node(int nid)
{
int error;
int cpu;
+ int onid;
struct node *node;
+ struct node_access_nodes *acc;
node = kzalloc(sizeof(struct node), GFP_KERNEL);
if (!node)
@@ -887,6 +889,20 @@ int __register_one_node(int nid)
node_init_caches(nid);
+ /*
+ * for each cpu node - add accessor to this node
+ * if this is a cpu node, add accessor to each other node
+ */
+ for_each_online_node(onid) {
+ /* During system bringup nodes may not be fully initialized */
+ if (!node_devices[onid])
+ continue;
+ if (node_state(onid, N_CPU))
+ acc = node_init_node_access(node, onid);
+ if (node_state(nid, N_CPU))
+ acc = node_init_node_access(node_devices[onid], nid);
+ }
+
return error;
}
--
2.39.1
next prev parent reply other threads:[~2023-10-31 0:38 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 0:38 [RFC PATCH v3 0/4] Node Weights and Weighted Interleave Gregory Price
2023-10-31 0:38 ` [RFC PATCH v3 1/4] base/node.c: initialize the accessor list before registering Gregory Price
2023-10-31 0:38 ` Gregory Price [this message]
2023-10-31 0:38 ` [RFC PATCH v3 3/4] node: add interleave weights to node accessor Gregory Price
2023-10-31 0:38 ` [RFC PATCH v3 4/4] mm/mempolicy: modify interleave mempolicy to use node weights Gregory Price
2023-10-31 17:52 ` [EXT] " Srinivasulu Thanneeru
2023-10-31 18:23 ` Srinivasulu Thanneeru
2023-10-31 9:53 ` [RFC PATCH v3 0/4] Node Weights and Weighted Interleave Michal Hocko
2023-10-31 15:21 ` Johannes Weiner
2023-10-31 15:56 ` Michal Hocko
2023-10-31 4:27 ` Gregory Price
2023-11-01 13:45 ` Michal Hocko
2023-11-01 16:58 ` Gregory Price
2023-11-02 9:47 ` Michal Hocko
2023-11-02 3:18 ` Gregory Price
2023-11-03 7:45 ` Huang, Ying
2023-11-03 14:16 ` Jonathan Cameron
2023-11-06 3:20 ` Huang, Ying
2023-11-03 9:56 ` Michal Hocko
2023-11-02 18:21 ` Gregory Price
2023-11-03 16:59 ` Michal Hocko
2023-11-02 2:01 ` Huang, Ying
2023-10-31 16:22 ` Johannes Weiner
2023-10-31 4:29 ` Gregory Price
2023-11-01 2:34 ` Huang, Ying
2023-11-01 9:29 ` Ravi Jonnalagadda
2023-11-02 6:41 ` Huang, Ying
2023-11-02 9:35 ` Ravi Jonnalagadda
2023-11-02 14:13 ` Jonathan Cameron
2023-11-03 7:00 ` Huang, Ying
2023-11-01 13:56 ` Michal Hocko
2023-11-02 6:21 ` Huang, Ying
2023-11-02 9:30 ` Michal Hocko
2023-11-01 2:21 ` Huang, Ying
2023-11-01 14:01 ` Michal Hocko
2023-11-02 6:11 ` Huang, Ying
2023-11-02 9:28 ` Michal Hocko
2023-11-03 7:10 ` Huang, Ying
2023-11-03 9:39 ` Michal Hocko
2023-11-06 5:08 ` Huang, Ying
-- strict thread matches above, loose matches on Subject: below --
2023-10-31 0:17 [RFC PATCH v3 0/4] Weighted Interleave and Node Weights Gregory Price
2023-10-31 0:17 ` [RFC PATCH v3 2/4] node: add accessors to sysfs when nodes are created Gregory Price
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=20231031003810.4532-3-gregory.price@memverge.com \
--to=gourry.memverge@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=apopple@nvidia.com \
--cc=dave.hansen@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=gregory.price@memverge.com \
--cc=hannes@cmpxchg.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=rafael@kernel.org \
--cc=shy828301@gmail.com \
--cc=tim.c.chen@intel.com \
--cc=weixugc@google.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