From: Andrew Morton <akpm@linux-foundation.org>
To: <xu.xin16@zte.com.cn>
Cc: <david@kernel.org>, <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>
Subject: Re: ksm: initialize rmap values directly and make them const
Date: Fri, 6 Feb 2026 07:39:42 -0800 [thread overview]
Message-ID: <20260206073942.e37ce92b81f0a0c51a1f5b82@linux-foundation.org> (raw)
In-Reply-To: <20260206163850402hEblYPDgLSG4M7CT1ju2G@zte.com.cn>
On Fri, 6 Feb 2026 16:38:50 +0800 (CST) <xu.xin16@zte.com.cn> wrote:
> > >
> > > Fixes: 06fbd555dea8 ("ksm: optimize rmap_walk_ksm by passing a suitable addressrange")
> > > Signed-off-by: xu xin <xu.xin16@zte.com.cn>
> >
> > The patch does not seem to be upstream / in mm-stable yet.
> >
> > Can you resend the original patch with these changes included and the
> > reproducer referenced in the updated patch description?
>
> Sure, I thought the original patch was merged in linux-next.
I've recently moved the original series into mm.git's mm-new branch, which
isn't included in linux-next. Because it appeared that the v2 series
wouldn't be available in time for the next merge window.
It is a wonderful performance improvement, but I think it's best that
we revisit the series for the next -rc cycle. So can you please
integrate this new change into "ksm: optimize rmap_walk_ksm by passing
a suitable addressrange", rework the changelogs to reflect the
discussion thus far and resend the "KSM: Optimizations for
rmap_walk_ksm" series?
next prev parent reply other threads:[~2026-02-06 15:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 7:22 xu.xin16
2026-02-06 8:18 ` David Hildenbrand (Arm)
2026-02-06 8:38 ` xu.xin16
2026-02-06 8:46 ` David Hildenbrand (Arm)
2026-02-06 15:39 ` Andrew Morton [this message]
2026-02-06 15:29 ` Matthew Wilcox
2026-02-06 17:34 ` David Hildenbrand (Arm)
2026-02-06 18:09 ` David Hildenbrand (Arm)
2026-02-06 18:49 ` Matthew Wilcox
2026-02-06 18:57 ` David Hildenbrand (Arm)
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=20260206073942.e37ce92b81f0a0c51a1f5b82@linux-foundation.org \
--to=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 \
--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