From: Muchun Song <muchun.song@linux.dev>
To: David Hildenbrand <david@redhat.com>
Cc: Muchun Song <songmuchun@bytedance.com>,
Greg KH <gregkh@linuxfoundation.org>,
rafael@kernel.org, Mike Kravetz <mike.kravetz@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Oscar Salvador <osalvador@suse.de>,
ying.huang@intel.com, aneesh.kumar@linux.ibm.com,
David Rientjes <rientjes@google.com>,
linux-kernel@vger.kernel.org, Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH v3] mm: hugetlb: eliminate memory-less nodes handling
Date: Tue, 13 Sep 2022 17:57:15 +0800 [thread overview]
Message-ID: <BC89CDF2-D3BA-42DF-B73B-9E765A865F10@linux.dev> (raw)
In-Reply-To: <b8d2fe17-93e6-743a-73c4-e8b22964704b@redhat.com>
> On Sep 8, 2022, at 20:21, David Hildenbrand <david@redhat.com> wrote:
>
> On 08.09.22 09:58, Muchun Song wrote:
>> The memory-notify-based approach aims to handle meory-less nodes, however, it just adds
>> the complexity of code as pointed by David in thread [1]. The handling of memory-less
>> nodes is introduced by commit 4faf8d950ec4 ("hugetlb: handle memory hot-plug events").
>> From its commit message, we cannot find any necessity of handling this case. So, we can
>> simply register/unregister sysfs entries in register_node/unregister_node to simlify the
>> code.
>> BTW, hotplug callback added because in hugetlb_register_all_nodes() we register sysfs
>> nodes only for N_MEMORY nodes, seeing commit 9b5e5d0fdc91, which said it was a preparation
>> for handling memory-less nodes via memory hotplug. Since we want to remove memory hotplug,
>> so make sure we only register per-node sysfs for online (N_ONLINE) nodes in
>> hugetlb_register_all_nodes().
>> https://lore.kernel.org/linux-mm/60933ffc-b850-976c-78a0-0ee6e0ea9ef0@redhat.com/ [1]
>> Suggested-by: David Hildenbrand <david@redhat.com>
>> Signed-off-by: Muchun Song <songmuchun@bytedance.com>
>> ---
>> v3:
>> - Fix 'struct node' is not declared reported by LTP.
>> v2:
>> - Move declaration of function related to hugetlb to hugetlb.h (David).
>> - Introduce hugetlb_sysfs_initialized() and call it from hugetlb_sysfs_init() (David).
>> - Move hugetlb_register_all_nodes() into hugetlb_sysfs_init() (David).
>> - Fix implicit-function-declaration reported by LKP.
>> - Register per-node sysfs for online (N_ONLINE) nodes instead of N_MEMORY (Aneesh).
>> drivers/base/node.c | 8 +++--
>> include/linux/hugetlb.h | 14 +++++++++
>> mm/hugetlb.c | 81 ++++++++++++++++++++++---------------------------
>> 3 files changed, 57 insertions(+), 46 deletions(-)
>
>
>
>> --- a/mm/hugetlb.c
>> +++ b/mm/hugetlb.c
>> @@ -3880,24 +3880,14 @@ static int hugetlb_sysfs_add_hstate(struct hstate *h, struct kobject *parent,
>> return 0;
>> }
>> -static void __init hugetlb_sysfs_init(void)
>> -{
>> - struct hstate *h;
>> - int err;
>> -
>> - hugepages_kobj = kobject_create_and_add("hugepages", mm_kobj);
>> - if (!hugepages_kobj)
>> - return;
>> +#ifdef CONFIG_NUMA
>> +static bool hugetlb_sysfs_initialized __ro_after_init;
>> - for_each_hstate(h) {
>> - err = hugetlb_sysfs_add_hstate(h, hugepages_kobj,
>> - hstate_kobjs, &hstate_attr_group);
>> - if (err)
>> - pr_err("HugeTLB: Unable to add hstate %s", h->name);
>> - }
>> +static inline void hugetlb_mark_sysfs_initialized(void)
>> +{
>> + hugetlb_sysfs_initialized = true;
>> }
>
> Do we really need a separate function for this? Why not simply always set that from hugetlb_sysfs_init() ?
I can remove this helper.
>
> I'm also not sure if we really want to optimize out one variable for !CONFIG_NUMA.
Either is fine to me. I think the optimization does not bring any complexity.
So I’ll keep it the same in the next version unless anyone is against this.
>
> Anyhow, in general
>
> Acked-by: David Hildenbrand <david@redhat.com>
Thanks David.
>
>
> --
> Thanks,
>
> David / dhildenb
>
prev parent reply other threads:[~2022-09-13 9:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 7:58 [PATCH v3] mm: hugetlb: eliminate memory-less nodes handling Muchun Song
2022-09-08 12:21 ` David Hildenbrand
2022-09-13 9:57 ` Muchun Song [this message]
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=BC89CDF2-D3BA-42DF-B73B-9E765A865F10@linux.dev \
--to=muchun.song@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=osalvador@suse.de \
--cc=rafael@kernel.org \
--cc=rientjes@google.com \
--cc=songmuchun@bytedance.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).