From: <yang.yang29@zte.com.cn>
To: <xu.xin16@zte.com.cn>
Cc: <akpm@linux-foundation.org>, <david@kernel.org>,
<chengming.zhou@linux.dev>, <hughd@google.com>,
<wang.yaxin@zte.com.cn>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] ksm: Optimize rmap_walk_ksm by passing a suitable address range
Date: Thu, 15 Jan 2026 15:34:13 +0800 (CST) [thread overview]
Message-ID: <20260115153413416ZHFvu9Uuv-HbyU9UKguyW@zte.com.cn> (raw)
> + pgoff_start = rmap_item->address >> PAGE_SHIFT;
> + pgoff_end = pgoff_start + folio_nr_pages(folio) - 1;
> +
> anon_vma_interval_tree_foreach(vmac, &anon_vma->rb_root,
> - 0, ULONG_MAX) {
> + pgoff_start, pgoff_end) {
Good job.
I see there is another similar situations in collect_procs_ksm().
We can simulate memory errors by calling the memory_failure().
next reply other threads:[~2026-01-15 7:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 7:34 yang.yang29 [this message]
[not found] <20260112215315996jocrkFSqeYfhABkZxqs4T@zte.com.cn>
2026-01-12 14:01 ` xu.xin16
2026-01-12 17:47 ` Andrew Morton
2026-01-12 19:25 ` David Hildenbrand (Red Hat)
2026-01-14 2:40 ` xu.xin16
2026-01-14 10:24 ` David Hildenbrand (Red Hat)
2026-01-15 1:41 ` xu.xin16
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=20260115153413416ZHFvu9Uuv-HbyU9UKguyW@zte.com.cn \
--to=yang.yang29@zte.com.cn \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=david@kernel.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wang.yaxin@zte.com.cn \
--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