From: "Li, Tianyou" <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>,
Chen Zhang <zhangchen.kidd@jd.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v7 0/2] Optimize zone->contiguous update and issue fix
Date: Mon, 5 Jan 2026 20:21:53 +0800 [thread overview]
Message-ID: <011e2691-994f-4038-adf0-02e899eca777@intel.com> (raw)
In-Reply-To: <20251222145807.11351-1-tianyou.li@intel.com>
Happy New Year!
Appreciated for your review and looking forward for the comments. Thanks.
Regards,
Tianyou
On 12/22/2025 10:58 PM, Tianyou Li wrote:
> This series contains 2 patches, the first one fix an issue when check
> the zone->contiguous during zone grows, the second one add a fast path
> to check the zone->contiguous. The issue fixed by the first patch can
> be found in the original code path without the second patch.
>
> Yuan Liu (1):
> mm/memory hotplug: fix zone->contiguous always false when hotplug
>
> Tianyou Li (1):
> mm/memory hotplug/unplug: Optimize zone->contiguous update when
> changes pfn range
>
>
> Changes History
> ===============
> v2 changes:
> Add check_zone_contiguous_fast function to check zone contiguity for
> new memory PFN ranges.
>
> v3 changes:
> Add zone contiguity check for empty zones.
>
> v4 changes:
> 1. Improve coding style.
> 2. Add fast path for zone contiguity check in memory unplugged cases,
> and update test results.
> 3. Refactor set_zone_contiguous: the new set_zone_contiguous updates
> zone contiguity based on the fast path results.
>
> v5 changes:
> 1. Improve coding style.
> 2. Fix a issue in which zone->contiguous was always false when adding
> new memory, leveraging the fast path optimization.
>
> v6 changes:
> 1. Improve coding style.
> 2. Add comments.
>
> v7 changes:
> 1. Rebased to 6.19-rc1
> 2. Reorder the patches so that the fix will be the first in the series.
>
> Tianyou Li (2):
> mm/memory hotplug: fix zone->contiguous always false when hotplug
> mm/memory hotplug/unplug: Optimize zone->contiguous update when
> changes pfn range
>
> mm/internal.h | 8 ++++-
> mm/memory_hotplug.c | 75 +++++++++++++++++++++++++++++++++++++++++++--
> mm/mm_init.c | 12 ++++++--
> 3 files changed, 89 insertions(+), 6 deletions(-)
>
next prev parent reply other threads:[~2026-01-05 12:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 14:58 Tianyou Li
2025-12-22 14:58 ` [PATCH v7 1/2] mm/memory hotplug: fix zone->contiguous always false when hotplug Tianyou Li
2026-01-06 20:03 ` David Hildenbrand (Red Hat)
2025-12-22 14:58 ` [PATCH v7 2/2] mm/memory hotplug/unplug: Optimize zone->contiguous update when changes pfn range Tianyou Li
2026-01-06 20:18 ` David Hildenbrand (Red Hat)
2026-01-06 20:25 ` David Hildenbrand (Red Hat)
2026-01-05 12:21 ` Li, Tianyou [this message]
2026-01-05 16:27 ` [PATCH v7 0/2] Optimize zone->contiguous update and issue fix David Hildenbrand (Red Hat)
2026-01-06 3:48 ` 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=011e2691-994f-4038-adf0-02e899eca777@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