From: Tianyou Li <tianyou.li@intel.com>
To: David Hildenbrand <david@redhat.com>,
Oscar Salvador <osalvador@suse.de>,
Mike Rapoport <rppt@kernel.org>,
Wei Yang <richard.weiyang@gmail.com>
Cc: linux-mm@kvack.org, Yong Hu <yong.hu@intel.com>,
Nanhai Zou <nanhai.zou@intel.com>, Yuan Liu <yuan1.liu@intel.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
Qiuxu Zhuo <qiuxu.zhuo@intel.com>,
Yu C Chen <yu.c.chen@intel.com>, Pan Deng <pan.deng@intel.com>,
Tianyou Li <tianyou.li@intel.com>,
Chen Zhang <zhangchen.kidd@jd.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v5 0/2] Optimize zone->contiguous update and issue fix
Date: Mon, 8 Dec 2025 23:25:42 +0800 [thread overview]
Message-ID: <20251208152544.1150732-1-tianyou.li@intel.com> (raw)
This series contains 2 patches, the first one add a fast path to check
the zone->contiguous, the second one fix an issue when check the
zone->contiguous at the slow path during zone grows. The issue fixed
by the second patch can be found in the original code path without the
first patch.
Tianyou Li (1):
mm/memory hotplug/unplug: Optimize zone->contiguous update when
changes pfn range
Yuan Liu (1):
mm/memory hotplug: fix zone->contiguous always false when hotplug
mm/internal.h | 8 +++++-
mm/memory_hotplug.c | 70 +++++++++++++++++++++++++++++++++++++++++++--
mm/mm_init.c | 13 +++++++--
3 files changed, 85 insertions(+), 6 deletions(-)
--
2.47.1
next reply other threads:[~2025-12-08 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 15:25 Tianyou Li [this message]
2025-12-08 15:25 ` [PATCH v5 1/2] mm/memory hotplug/unplug: Optimize zone->contiguous update when changes pfn range Tianyou Li
2025-12-11 5:07 ` Oscar Salvador
2025-12-12 5:27 ` Li, Tianyou
2025-12-19 1:31 ` Li, Tianyou
2025-12-08 15:25 ` [PATCH v5 2/2] mm/memory hotplug: fix zone->contiguous always false when hotplug Tianyou Li
2025-12-11 5:16 ` Oscar Salvador
2025-12-12 5:35 ` Li, Tianyou
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=20251208152544.1150732-1-tianyou.li@intel.com \
--to=tianyou.li@intel.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nanhai.zou@intel.com \
--cc=osalvador@suse.de \
--cc=pan.deng@intel.com \
--cc=qiuxu.zhuo@intel.com \
--cc=richard.weiyang@gmail.com \
--cc=rppt@kernel.org \
--cc=tim.c.chen@linux.intel.com \
--cc=yong.hu@intel.com \
--cc=yu.c.chen@intel.com \
--cc=yuan1.liu@intel.com \
--cc=zhangchen.kidd@jd.com \
/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