[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53F15E33.40705@huawei.com>
Date: Mon, 18 Aug 2014 10:00:19 +0800
From: Xishi Qiu <qiuxishi@...wei.com>
To: Tejun Heo <tj@...nel.org>
CC: Andrew Morton <akpm@...ux-foundation.org>,
Tang Chen <tangchen@...fujitsu.com>,
Zhang Yanfei <zhangyanfei@...fujitsu.com>,
"Wen Congyang" <wency@...fujitsu.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
"H. Peter Anvin" <hpa@...or.com>, Linux MM <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mem-hotplug: let memblock skip the hotpluggable memory
regions in __next_mem_range()
On 2014/8/17 19:08, Tejun Heo wrote:
> Hello,
>
> On Sat, Aug 16, 2014 at 10:36:41PM +0800, Xishi Qiu wrote:
>> numa_clear_node_hotplug()? There is only numa_clear_kernel_node_hotplug().
>
> Yeah, that one.
>
>> If we don't clear hotpluggable flag in free_low_memory_core_early(), the
>> memory which marked hotpluggable flag will not free to buddy allocator.
>> Because __next_mem_range() will skip them.
>>
>> free_low_memory_core_early
>> for_each_free_mem_range
>> for_each_mem_range
>> __next_mem_range
>
> Ah, okay, so the patch fixes __next_mem_range() and thus makes
> free_low_memory_core_early() to skip hotpluggable regions unlike
> before. Please explain things like that in the changelog. Also,
OK, I will send V2.
Thanks,
Xishi Qiu
> what's its relationship with numa_clear_kernel_node_hotplug()? Do we
> still need them? If so, what are the different roles that these two
> separate places serve?
>
> Thanks.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists