linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Honggyu Kim <honggyu.kim@sk.com>
To: David Hildenbrand <david@redhat.com>,
	Rakie Kim <rakie.kim@sk.com>,
	akpm@linux-foundation.org
Cc: kernel_team@skhynix.com, 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, Jonathan.Cameron@huawei.com,
	osalvador@suse.de, yunjeong.mun@sk.com
Subject: Re: [PATCH v7 3/3] mm/mempolicy: Support memory hotplug in weighted interleave
Date: Wed, 9 Apr 2025 20:39:47 +0900	[thread overview]
Message-ID: <b58f2dd6-d978-487a-b420-badfb4847c00@sk.com> (raw)
In-Reply-To: <19562f7e-38ce-41fc-8dfc-bfd6b1259291@redhat.com>

Hi David,

On 4/9/2025 6:05 PM, David Hildenbrand wrote:
> On 08.04.25 09:32, Rakie Kim wrote:
>> The weighted interleave policy distributes page allocations across multiple
>> NUMA nodes based on their performance weight, thereby improving memory
>> bandwidth utilization. The weight values for each node are configured
>> through sysfs.
>>
>> Previously, sysfs entries for configuring weighted interleave were created
>> for all possible nodes (N_POSSIBLE) at initialization, including nodes that
>> might not have memory. However, not all nodes in N_POSSIBLE are usable at
>> runtime, as some may remain memoryless or offline.
>> This led to sysfs entries being created for unusable nodes, causing
>> potential misconfiguration issues.
>>
>> To address this issue, this patch modifies the sysfs creation logic to:
>> 1) Limit sysfs entries to nodes that are online and have memory, avoiding
>>     the creation of sysfs entries for nodes that cannot be used.
>> 2) Support memory hotplug by dynamically adding and removing sysfs entries
>>     based on whether a node transitions into or out of the N_MEMORY state.
>>
>> Additionally, the patch ensures that sysfs attributes are properly managed
>> when nodes go offline, preventing stale or redundant entries from persisting
>> in the system.
>>
>> By making these changes, the weighted interleave policy now manages its
>> sysfs entries more efficiently, ensuring that only relevant nodes are
>> considered for interleaving, and dynamically adapting to memory hotplug
>> events.
>>
>> 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>
> 
> 
> Why are the other SOF in there? Are there Co-developed-by missing?

I initially found the problem and fixed it with my internal implementation but
Rakie also had his idea so he started working on it.  His initial implementation
has almost been similar to mine.

I thought Signed-off-by is a way to express the patch series contains our
contribution, but if you think it's unusual, then I can add this.

   Co-developed-by: Honggyu Kim <honggyu.kim@sk.com>
   Signed-off-by: Honggyu Kim <honggyu.kim@sk.com>

For Yunjeong, the following can be added.

   Tested-by: Yunjeong Mun <yunjeong.mun@sk.com>

However, this patch series is already in Andrew's mm-new so I don't want to
bother him again unless we need to update this patches for other reasons.

Is this okay?

Thanks,
Honggyu

> 
> 
> Acked-by: David Hildenbrand <david@redhat.com>
> 



  reply	other threads:[~2025-04-09 11:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08  7:32 [PATCH v7 0/3] Enhance sysfs handling for " Rakie Kim
2025-04-08  7:32 ` [PATCH v7 1/3] mm/mempolicy: Fix memory leaks in weighted interleave sysfs Rakie Kim
2025-04-08 13:45   ` Joshua Hahn
2025-04-15 15:41   ` Jonathan Cameron
2025-04-08  7:32 ` [PATCH v7 2/3] mm/mempolicy: Prepare weighted interleave sysfs for memory hotplug Rakie Kim
2025-04-08 13:49   ` Joshua Hahn
2025-04-09  3:43   ` Dan Williams
2025-04-09  3:54     ` Dan Williams
2025-04-09  5:56       ` Rakie Kim
2025-04-09 18:51         ` Dan Williams
2025-04-10  7:53           ` Rakie Kim
2025-04-10  8:06             ` Rakie Kim
2025-04-11  3:11               ` Andrew Morton
2025-04-11  7:21       ` Rakie Kim
2025-04-11 22:24         ` Dan Williams
2025-04-08  7:32 ` [PATCH v7 3/3] mm/mempolicy: Support memory hotplug in weighted interleave Rakie Kim
2025-04-08 13:52   ` Joshua Hahn
2025-04-08 14:45   ` Gregory Price
2025-04-09  9:05   ` David Hildenbrand
2025-04-09 11:39     ` Honggyu Kim [this message]
2025-04-09 11:52       ` David Hildenbrand
2025-04-10  7:53         ` Rakie Kim
2025-04-10 13:25         ` Honggyu Kim
2025-04-10 13:41           ` David Hildenbrand
2025-04-15 16:00   ` Jonathan Cameron
2025-04-16  4:04     ` Honggyu Kim
2025-04-16  7:37       ` Honggyu Kim
2025-04-16  7:49       ` Rakie Kim

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=b58f2dd6-d978-487a-b420-badfb4847c00@sk.com \
    --to=honggyu.kim@sk.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=david@redhat.com \
    --cc=gourry@gourry.net \
    --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