From: Dan Williams <dan.j.williams@intel.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Rakie Kim <rakie.kim@sk.com>
Cc: <akpm@linux-foundation.org>, <gourry@gourry.net>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<linux-cxl@vger.kernel.org>, <joshua.hahnjy@gmail.com>,
<dan.j.williams@intel.com>, <ying.huang@linux.alibaba.com>,
<david@redhat.com>, <osalvador@suse.de>,
<kernel_team@skhynix.com>, <honggyu.kim@sk.com>,
<yunjeong.mun@sk.com>
Subject: Re: [PATCH v6 2/3] mm/mempolicy: Prepare weighted interleave sysfs for memory hotplug
Date: Fri, 4 Apr 2025 10:23:10 -0700 [thread overview]
Message-ID: <67f0157e498c9_464ec294df@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20250404140559.00001112@huawei.com>
Jonathan Cameron wrote:
> On Fri, 4 Apr 2025 16:46:20 +0900
> Rakie Kim <rakie.kim@sk.com> wrote:
>
> > Previously, the weighted interleave sysfs structure was statically
> > managed during initialization. This prevented new nodes from being
> > recognized when memory hotplug events occurred, limiting the ability
> > to update or extend sysfs entries dynamically at runtime.
> >
> > To address this, this patch refactors the sysfs infrastructure and
> > encapsulates it within a new structure, `sysfs_wi_group`, which holds
> > both the kobject and an array of node attribute pointers.
> >
> > By allocating this group structure globally, the per-node sysfs
> > attributes can be managed beyond initialization time, enabling
> > external modules to insert or remove node entries in response to
> > events such as memory hotplug or node online/offline transitions.
> >
> > Instead of allocating all per-node sysfs attributes at once, the
> > initialization path now uses the existing sysfs_wi_node_add() and
> > sysfs_wi_node_delete() helpers. This refactoring makes it possible
> > to modularly manage per-node sysfs entries and ensures the
> > infrastructure is ready for runtime extension.
> >
> > Signed-off-by: Rakie Kim <rakie.kim@sk.com>
> > Signed-off-by: Honggyu Kim <honggyu.kim@sk.com>
> > Signed-off-by: Yunjeong Mun <yunjeong.mun@sk.com>
> > Reviewed-by: Gregory Price <gourry@gourry.net>
> Hi Rakie,
>
> Some things I was requesting in patch 1 are done here.
> Mostly I think what is wanted is moving some of that
> refactoring back to that patch rather than here.
>
> Some of the label and function naming needs another look.
>
> Jonathan
[..]
> > @@ -3430,27 +3437,24 @@ static ssize_t node_store(struct kobject *kobj, struct kobj_attribute *attr,
> > return count;
> > }
> >
> > -static struct iw_node_attr **node_attrs;
> > -
> > -static void sysfs_wi_node_release(struct iw_node_attr *node_attr,
> > - struct kobject *parent)
> > +static void sysfs_wi_node_delete(int nid)
>
> Maybe stick to release naming to match the sysfs_wi_release()
> below? I don't really care about this.
I had asked for "delete" to pair with "add" and to not get confused with
a final kobject_put() callback.
next prev parent reply other threads:[~2025-04-04 17:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 7:46 [PATCH v6 0/3] Enhance sysfs handling for memory hotplug in weighted interleave Rakie Kim
2025-04-04 7:46 ` [PATCH v6 1/3] mm/mempolicy: Fix memory leaks in weighted interleave sysfs Rakie Kim
2025-04-04 12:59 ` Jonathan Cameron
2025-04-07 9:37 ` Rakie Kim
2025-04-04 7:46 ` [PATCH v6 2/3] mm/mempolicy: Prepare weighted interleave sysfs for memory hotplug Rakie Kim
2025-04-04 13:05 ` Jonathan Cameron
2025-04-04 17:23 ` Dan Williams [this message]
2025-04-07 9:38 ` Rakie Kim
2025-04-07 9:49 ` Jonathan Cameron
2025-04-04 7:46 ` [PATCH v6 3/3] mm/mempolicy: Support memory hotplug in weighted interleave Rakie Kim
2025-04-04 8:43 ` Oscar Salvador
2025-04-07 9:37 ` Rakie Kim
2025-04-04 20:45 ` David Hildenbrand
2025-04-07 9:39 ` Rakie Kim
2025-04-07 10:47 ` David Hildenbrand
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=67f0157e498c9_464ec294df@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=gourry@gourry.net \
--cc=honggyu.kim@sk.com \
--cc=joshua.hahnjy@gmail.com \
--cc=kernel_team@skhynix.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=rakie.kim@sk.com \
--cc=ying.huang@linux.alibaba.com \
--cc=yunjeong.mun@sk.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