From: Donet Tom <donettom@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Ritesh Harjani <ritesh.list@gmail.com>,
Xu Xin <xu.xin16@zte.com.cn>,
Chengming Zhou <chengming.zhou@linux.dev>,
Wei Yang <richard.weiyang@gmail.com>,
Aboorva Devarajan <aboorvad@linux.ibm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mm/ksm: Reset KSM counters in mm_struct during fork
Date: Wed, 27 Aug 2025 23:33:05 +0530 [thread overview]
Message-ID: <f850ea7f-d2dc-4cc9-83ba-871d19311fa8@linux.ibm.com> (raw)
In-Reply-To: <59fef25c-6559-4fb3-8810-c2a7dd36b95a@redhat.com>
On 8/26/25 6:49 PM, David Hildenbrand wrote:
> On 26.08.25 14:49, Donet Tom wrote:
>> Currently, the KSM-related counters in `mm_struct` such as
>> `ksm_merging_pages`, `ksm_rmap_items`, and `ksm_zero_pages` are
>> inherited by the child process during fork. This results in
>> incorrect accounting, since the child has not performed any
>> KSM page merging.
>
> So, the situation is that our child process maps these pages, but it
> does not have any stable rmap items corresponding to these pages.
Yes
>
> rmap_walk_ksm() spells that case out.
>
> Can you clarify that in the description here, and how both stats
> correspond to rmap items?
Sure I will add it in next version.
>
> What is the effective result of this misacounting? I assume only a
> higher number than expected.
>
Yes the number will be higher than expected.
>
>
>>
>> To fix this, reset these counters to 0 in the newly created
>> `mm_struct` during fork. This ensures that KSM statistics
>> remain accurate and only reflect the activity of each process.
>>
>
> Fixes? CC stable?
I will add it in next version.
>
>> Signed-off-by: Donet Tom <donettom@linux.ibm.com>
>> ---
>> include/linux/ksm.h | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/include/linux/ksm.h b/include/linux/ksm.h
>> index 22e67ca7cba3..61b8892c632b 100644
>> --- a/include/linux/ksm.h
>> +++ b/include/linux/ksm.h
>> @@ -56,8 +56,12 @@ static inline long mm_ksm_zero_pages(struct
>> mm_struct *mm)
>> static inline void ksm_fork(struct mm_struct *mm, struct mm_struct
>> *oldmm)
>> {
>> /* Adding mm to ksm is best effort on fork. */
>> - if (mm_flags_test(MMF_VM_MERGEABLE, oldmm))
>> + if (mm_flags_test(MMF_VM_MERGEABLE, oldmm)) {
>> + mm->ksm_merging_pages = 0;
>> + mm->ksm_rmap_items = 0;
>> + atomic_long_set(&mm->ksm_zero_pages, 0);
>> __ksm_enter(mm);
>> + }
>> }
>> static inline int ksm_execve(struct mm_struct *mm)
>
>
next prev parent reply other threads:[~2025-08-27 18:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 12:49 [PATCH 1/2] mm/ksm: Reset KSM counters in mm_struct during fork Donet Tom
2025-08-26 12:49 ` [PATCH 2/2] selftests/mm: add fork inheritance test for ksm_merging_pages counter Donet Tom
2025-08-26 13:22 ` David Hildenbrand
2025-08-27 18:03 ` Donet Tom
2025-08-26 13:19 ` [PATCH 1/2] mm/ksm: Reset KSM counters in mm_struct during fork David Hildenbrand
2025-08-27 18:03 ` Donet Tom [this message]
2025-08-26 13:47 ` Giorgi Tchankvetadze
2025-08-26 14:09 ` David Hildenbrand
2025-08-27 18:09 ` Donet Tom
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=f850ea7f-d2dc-4cc9-83ba-871d19311fa8@linux.ibm.com \
--to=donettom@linux.ibm.com \
--cc=aboorvad@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=richard.weiyang@gmail.com \
--cc=ritesh.list@gmail.com \
--cc=xu.xin16@zte.com.cn \
/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).