From: Muchun Song <muchun.song@linux.dev>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Muchun Song <songmuchun@bytedance.com>,
rafael@kernel.org, Mike Kravetz <mike.kravetz@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Oscar Salvador <osalvador@suse.de>,
David Hildenbrand <david@redhat.com>,
linux-kernel@vger.kernel.org, Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: hugetlb: simplify per-node sysfs creation and removal
Date: Fri, 19 Aug 2022 14:56:56 +0800 [thread overview]
Message-ID: <0F3FE8B0-9ADB-423D-A2FE-2AF1A3A6E619@linux.dev> (raw)
In-Reply-To: <A0353CE2-D014-4B35-95F1-40345D1B66E6@linux.dev>
> On Aug 19, 2022, at 14:44, Muchun Song <muchun.song@linux.dev> wrote:
>
>
>
>> On Aug 19, 2022, at 14:32, Greg KH <gregkh@linuxfoundation.org> wrote:
>>
>> On Fri, Aug 19, 2022 at 01:21:37PM +0800, Muchun Song wrote:
>>> The following commit offload per-node sysfs creation and removal to a kworker and
>>> did not say why it is needed. And it also said "I don't know that this is
>>> absolutely required". It seems like the author was not sure as well. Since it
>>> only complicates the code, this patch will revert the changes to simplify the code.
>>>
>>> 39da08cb074c ("hugetlb: offload per node attribute registrations")
>>
>> Any specific reason why you did not cc: the original author of this
>> commit, or anyone else on the patch?
>
> OK. Cc Lee Schermerhorn.
Unluckily, I guess the email address is out of date since I just got bounced mail
(Undelivered Mail Returned to Sender). Remove lee.schermerhorn@hp.com from the
Cc list.
>
>>
>>> We could use memory hotplug notifier to do per-node sysfs creation and removal
>>> instead of inserting those operations to node registration and unregistration.
>>> Then, it can reduce the code coupling between node.c and hugetlb.c. Also, it can
>>> simplify the code.
>>
>> I do not think we had memory hotplug notifier back in 2009 when this
>> commit was first written.
>
> Maybe not. Commit 39da08cb074c is merger in 2009. However, hotplug notifier mechanism
> is merged in 2006. The document is updated in 2007 (see commit 10020ca246c5).
>
>>
>> How did you test this? Did you use a HUGETLBFS system and verify that
>> everything still works properly? You are deleting a lot of code (always
>> nice), but making sure everything is still operating the same is a good
>> thing.
>
> I really did the test (through a VM), it works properly.
>
> Thanks.
>
>>
>> thanks,
>>
>> greg k-h
next prev parent reply other threads:[~2022-08-19 6:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 5:21 [PATCH] mm: hugetlb: simplify per-node sysfs creation and removal Muchun Song
2022-08-19 6:32 ` Greg KH
2022-08-19 6:44 ` Muchun Song
2022-08-19 6:56 ` Muchun Song [this message]
2022-08-19 7:00 ` Greg KH
2022-08-19 7:15 ` Muchun Song
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=0F3FE8B0-9ADB-423D-A2FE-2AF1A3A6E619@linux.dev \
--to=muchun.song@linux.dev \
--cc=akpm@linux-foundation.org \
--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=songmuchun@bytedance.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.