From: <xu.xin16@zte.com.cn>
To: <david@kernel.org>, <akpm@linux-foundation.org>
Cc: <chengming.zhou@linux.dev>, <hughd@google.com>,
<wang.yaxin@zte.com.cn>, <yang.yang29@zte.com.cn>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<xu.xin16@zte.com.cn>
Subject: [PATCH v2 0/2] KSM: Optimizations for rmap_walk_ksm
Date: Fri, 6 Feb 2026 17:56:09 +0800 (CST) [thread overview]
Message-ID: <20260206175609696_A7uH3a1F7VmQN-iTzjC3@zte.com.cn> (raw)
From: xu xin <xu.xin16@zte.com.cn>
There are two perfomance optimization patches for rmap_walk_ksm.
The patch [1/2] move the initializaion of addr from the position inside loop
to the position before the loop, since the variable will not change in the
loop.
The patch [2/2] optimize rmap_walk_ksm by passing a suitable page offset range
to the anon_vma_interval_tree_foreach loop to reduce ineffective checks.
The metric performance is seen at patch[2/2].
xu xin (2):
ksm: Initialize the addr only once in rmap_walk_ksm
ksm: Optimize rmap_walk_ksm by passing a suitable address range
mm/ksm.c | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
--
2.25.1
next reply other threads:[~2026-02-06 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 9:56 xu.xin16 [this message]
2026-02-06 9:57 ` [PATCH v2 1/2] ksm: Initialize the addr only once in rmap_walk_ksm xu.xin16
2026-02-06 10:46 ` David Hildenbrand (Arm)
2026-02-06 10:01 ` [PATCH v2 2/2] ksm: Optimize rmap_walk_ksm by passing a suitable address range xu.xin16
2026-02-06 11:01 ` David Hildenbrand (Arm)
2026-02-06 16:15 ` xu.xin16
2026-02-06 10:47 ` [PATCH v2 0/2] KSM: Optimizations for rmap_walk_ksm David Hildenbrand (Arm)
-- strict thread matches above, loose matches on Subject: below --
2026-02-06 9:55 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=20260206175609696_A7uH3a1F7VmQN-iTzjC3@zte.com.cn \
--to=xu.xin16@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=yang.yang29@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