From: "David Hildenbrand (Arm)" <david@kernel.org>
To: xu.xin16@zte.com.cn, akpm@linux-foundation.org
Cc: chengming.zhou@linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 2/2] mm/ksm: Use precise linear_page_index instead of the whole address space
Date: Thu, 9 Jul 2026 10:53:20 +0200 [thread overview]
Message-ID: <1cf4efb5-1876-482e-8a92-a211570e91c8@kernel.org> (raw)
In-Reply-To: <20260709111055267XMDer8X5AKmOhy46TRjwa@zte.com.cn>
On 7/9/26 05:10, xu.xin16@zte.com.cn wrote:
>>> From: xu xin <xu.xin16@zte.com.cn>
>>>
>>> Since an earlier commit introduced the linear_page_index to struct
>>> ksm_rmap_item[1], allowing for optimizing the RMAP walk, we can use it
>>> to locate more precisely all processes that hit the KSM page, which will
>>> decrease a lot of unvalid iterations.
>>
>> It's awkward to reference a commit by a mailing list link. The other patch is
>> not upstream yet. Best to wait for that to go in first, so you can properly
>> reference the commit.
>
> Ok, I'm going to resend this after that referenced patch is upstream.
Alternatively, just mention that we now have linear_page_index available that we
can use here, without referring to the other patch/commit.
That would probably be cleanest.
--
Cheers,
David
prev parent reply other threads:[~2026-07-09 8:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 3:38 [PATCH RESEND 0/2] KSM: use linear_page_index in collect_procs_ksm() xu.xin16
2026-07-08 4:19 ` [PATCH 1/2] mm/ksm: Initialize the addr only once in collect_procs_ksm xu.xin16
2026-07-08 7:50 ` David Hildenbrand (Arm)
2026-07-08 7:53 ` David Hildenbrand (Arm)
2026-07-08 4:22 ` [PATCH RESEND 2/2] mm/ksm: Use precise linear_page_index instead of the whole address space xu.xin16
2026-07-08 7:52 ` David Hildenbrand (Arm)
2026-07-09 3:10 ` xu.xin16
2026-07-09 8:53 ` David Hildenbrand (Arm) [this message]
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=1cf4efb5-1876-482e-8a92-a211570e91c8@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 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.