linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Muchun Song <songmuchun@bytedance.com>
Cc: rafael@kernel.org, mike.kravetz@oracle.com,
	akpm@linux-foundation.org, osalvador@suse.de, david@redhat.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	muchun.song@linux.dev
Subject: Re: [PATCH] mm: hugetlb: simplify per-node sysfs creation and removal
Date: Fri, 19 Aug 2022 08:32:58 +0200	[thread overview]
Message-ID: <Yv8umgIXfbpMFukB@kroah.com> (raw)
In-Reply-To: <20220819052137.7985-1-songmuchun@bytedance.com>

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?

> 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.

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.

thanks,

greg k-h


  reply	other threads:[~2022-08-19  6:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19  5:21 Muchun Song
2022-08-19  6:32 ` Greg KH [this message]
2022-08-19  6:44   ` Muchun Song
2022-08-19  6:56     ` Muchun Song
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=Yv8umgIXfbpMFukB@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.kravetz@oracle.com \
    --cc=muchun.song@linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox