From: Wei Yang <richard.weiyang@gmail.com>
To: David Hildenbrand <david@redhat.com>
Cc: Dev Jain <dev.jain@arm.com>, Lance Yang <lance.yang@linux.dev>,
Wei Yang <richard.weiyang@gmail.com>,
linux-mm@kvack.org, lorenzo.stoakes@oracle.com,
akpm@linux-foundation.org, chengming.zhou@linux.dev,
npache@redhat.com, ryan.roberts@arm.com, xu.xin16@zte.com.cn,
baohua@kernel.org, Liam.Howlett@oracle.com, ziy@nvidia.com,
baolin.wang@linux.alibaba.com
Subject: Re: [PATCH] mm/mm_slot: make sure slot is the first element of its wrapper structure
Date: Mon, 15 Sep 2025 09:15:42 +0000 [thread overview]
Message-ID: <20250915091542.gqqfdodrr6ztm3oh@master> (raw)
In-Reply-To: <62680957-e9aa-40ad-893d-885bd01e1117@redhat.com>
On Mon, Sep 15, 2025 at 09:56:34AM +0200, David Hildenbrand wrote:
[...]
>diff --git a/mm/khugepaged.c b/mm/khugepaged.c
>index 6b40bdfd224c3..70a32d59d7d2f 100644
>--- a/mm/khugepaged.c
>+++ b/mm/khugepaged.c
>@@ -488,11 +488,13 @@ void __khugepaged_exit(struct mm_struct *mm)
> spin_lock(&khugepaged_mm_lock);
> slot = mm_slot_lookup(mm_slots_hash, mm);
>- mm_slot = mm_slot_entry(slot, struct khugepaged_mm_slot, slot);
>- if (mm_slot && khugepaged_scan.mm_slot != mm_slot) {
>- hash_del(&slot->hash);
>- list_del(&slot->mm_node);
>- free = 1;
>+ if (slot) {
>+ mm_slot = mm_slot_entry(slot, struct khugepaged_mm_slot, slot);
>+ if (mm_slot && khugepaged_scan.mm_slot != mm_slot) {
>+ hash_del(&slot->hash);
>+ list_del(&slot->mm_node);
>+ free = 1;
>+ }
> }
But... to be honest, for khugepaged_mm_slot, I'd prefer to remove the
definition of it. struct khugepaged_mm_slot just wrap struct mm_slot.
One un-convenient thing of this change is we cant use KMEM_CACHE() to define
the slab allocator. Have to convert to the old api.
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2025-09-15 9:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-14 0:00 Wei Yang
2025-09-14 5:05 ` Lance Yang
2025-09-15 1:47 ` Wei Yang
2025-09-15 7:32 ` David Hildenbrand
2025-09-15 7:42 ` Wei Yang
2025-09-15 7:48 ` David Hildenbrand
2025-09-15 7:52 ` Wei Yang
2025-09-14 6:21 ` Dev Jain
2025-09-14 7:03 ` Lance Yang
2025-09-14 7:29 ` Dev Jain
2025-09-14 7:39 ` Lance Yang
2025-09-14 14:16 ` xu.xin16
2025-09-15 1:57 ` Wei Yang
2025-09-15 3:49 ` Dev Jain
2025-09-15 4:05 ` Dev Jain
2025-09-15 7:46 ` Wei Yang
2025-09-15 7:57 ` David Hildenbrand
2025-09-15 7:56 ` David Hildenbrand
2025-09-15 8:08 ` Lance Yang
2025-09-15 8:26 ` David Hildenbrand
2025-09-15 8:11 ` Dev Jain
2025-09-15 8:25 ` David Hildenbrand
2025-09-15 9:07 ` Wei Yang
2025-09-15 9:15 ` Wei Yang [this message]
2025-09-15 9:39 ` Kiryl Shutsemau
2025-09-15 13:37 ` Wei Yang
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=20250915091542.gqqfdodrr6ztm3oh@master \
--to=richard.weiyang@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=chengming.zhou@linux.dev \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=xu.xin16@zte.com.cn \
--cc=ziy@nvidia.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