linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Li, Tianyou" <tianyou.li@intel.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: David Hildenbrand <david@kernel.org>,
	Oscar Salvador <osalvador@suse.de>,
	Wei Yang <richard.weiyang@gmail.com>,
	Michal Hocko <mhocko@suse.com>, <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 v8 2/3] mm/memory hotplug/unplug: Add online_memory_block_pages() and offline_memory_block_pages()
Date: Wed, 28 Jan 2026 21:56:42 +0800	[thread overview]
Message-ID: <becccb16-c7bf-417d-a065-bb3a98eac88f@intel.com> (raw)
In-Reply-To: <aXhiJFvEKFk1Flpb@kernel.org>


On 1/27/2026 2:58 PM, Mike Rapoport wrote:
> On Sat, Jan 24, 2026 at 08:30:57PM +0800, Li, Tianyou wrote:
>> On 1/22/2026 7:32 PM, Mike Rapoport wrote:
>>>> diff --git a/drivers/base/memory.c b/drivers/base/memory.c
>>>> index 751f248ca4a8..ea4d6fbf34fd 100644
>>>> --- a/drivers/base/memory.c
>>>> +++ b/drivers/base/memory.c
>>>> @@ -246,31 +246,12 @@ static int memory_block_online(struct memory_block *mem)
>>>>    		nr_vmemmap_pages = mem->altmap->free;
>>>>    	mem_hotplug_begin();
>>>> -	if (nr_vmemmap_pages) {
>>>> -		ret = mhp_init_memmap_on_memory(start_pfn, nr_vmemmap_pages, zone);
>>>> -		if (ret)
>>>> -			goto out;
>>>> -	}
>>>> -
>>>> -	ret = online_pages(start_pfn + nr_vmemmap_pages,
>>>> -			   nr_pages - nr_vmemmap_pages, zone, mem->group);
>>>> -	if (ret) {
>>>> -		if (nr_vmemmap_pages)
>>>> -			mhp_deinit_memmap_on_memory(start_pfn, nr_vmemmap_pages);
>>>> -		goto out;
>>>> -	}
>>>> -
>>>> -	/*
>>>> -	 * Account once onlining succeeded. If the zone was unpopulated, it is
>>>> -	 * now already properly populated.
>>>> -	 */
>>>> -	if (nr_vmemmap_pages)
>>>> -		adjust_present_page_count(pfn_to_page(start_pfn), mem->group,
>>>> -					  nr_vmemmap_pages);
>>>> -
>>>> -	mem->zone = zone;
>>>> -out:
>>>> +	ret = online_memory_block_pages(start_pfn, nr_pages, nr_vmemmap_pages,
>>>> +					zone, mem->group);
>>>> +	if (!ret)
>>>> +		mem->zone = zone;
>>> I think we can move most of memory_block_online() to the new function and
>>> pass struct memory_block to it.
>>> I'd suggest
>>> 	
>>> 	int mhp_block_online(struct memory_block *block)
>>>
>>> and
>>>
>>> 	int mhp_block_offline(struct memory_block *block)
>>>
>>> Other than that LGTM.
>>
>> It's doable, if not other comments I can change the code. Would it look like
>> moving the functions to mm/memory_hotplug.c, change the name to
>> mhp_block_online() and mhp_block_offline(), and change the references where
>> the original function invoked in drivers/base/memory.c?
> Yeah, that's what I thought about.
>
> Even more broadly, I think the functionality in drivers/base/memory.c
> belongs to mm/ much more than to drivers/ but that's surely out of scope
> for these patches.
>   


Thanks Mike for the confirmation.


>> My prior thoughts on this was just break the code as small pieces as
>> necessary to handle the pages online part together with zone contiguous
>> state update.
> IMHO moving the entire function is cleaner, let's hear what David and Oscar
> think.


Sure. Actually the patch has been ready with the mhp_block_online() and 
mhp_block_offline() moved to memory_hotplug.c, the 
online_memory_block_pages() and offline_memory_block_pages() remains but 
as static function.


Once get feedback from David and Oscar, I can change them accordingly.



  reply	other threads:[~2026-01-28 13:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 14:33 [PATCH v8 0/3] Optimize zone->contiguous update and issue fix Tianyou Li
2026-01-20 14:33 ` [PATCH v8 1/3] mm/memory hotplug: Fix zone->contiguous always false when hotplug Tianyou Li
2026-01-22 11:16   ` Mike Rapoport
2026-01-24 12:18     ` Li, Tianyou
2026-01-26 21:58       ` Andrew Morton
2026-01-28 14:16         ` Li, Tianyou
2026-01-27  6:53       ` Mike Rapoport
2026-01-28 13:49         ` Li, Tianyou
2026-01-20 14:33 ` [PATCH v8 2/3] mm/memory hotplug/unplug: Add online_memory_block_pages() and offline_memory_block_pages() Tianyou Li
2026-01-22 11:32   ` Mike Rapoport
2026-01-24 12:30     ` Li, Tianyou
2026-01-27  6:58       ` Mike Rapoport
2026-01-28 13:56         ` Li, Tianyou [this message]
2026-01-20 14:33 ` [PATCH v8 3/3] mm/memory hotplug/unplug: Optimize zone->contiguous update when changes pfn range Tianyou Li
2026-01-22 11:43   ` Mike Rapoport
2026-01-24 12:43     ` Li, Tianyou
2026-01-27  7:10       ` Mike Rapoport
2026-01-28 14:11         ` 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=becccb16-c7bf-417d-a065-bb3a98eac88f@intel.com \
    --to=tianyou.li@intel.com \
    --cc=david@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --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