Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933110Ab2K0DZI (ORCPT ); Mon, 26 Nov 2012 22:25:08 -0500 Received: from szxga01-in.huawei.com ([119.145.14.64]:26236 "EHLO szxga01-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933066Ab2K0DZG (ORCPT ); Mon, 26 Nov 2012 22:25:06 -0500 Message-ID: <50B431E6.7060208@huawei.com> Date: Tue, 27 Nov 2012 11:22:14 +0800 From: Jianguo Wu User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Wen Congyang CC: "H. Peter Anvin" , Tang Chen , wujianguo , , , , , , , , , , , , , , , , Subject: Re: [PATCH v2 5/5] page_alloc: Bootmem limit with movablecore_map References: <1353667445-7593-1-git-send-email-tangchen@cn.fujitsu.com> <1353667445-7593-6-git-send-email-tangchen@cn.fujitsu.com> <50B36354.7040501@gmail.com> <50B36B54.7050506@cn.fujitsu.com> <50B38F69.6020902@zytor.com> <50B41041.6030902@huawei.com> <50B43150.2000405@cn.fujitsu.com> In-Reply-To: <50B43150.2000405@cn.fujitsu.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.135.74.216] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1759 Lines: 61 On 2012/11/27 11:19, Wen Congyang wrote: > At 11/27/2012 08:58 AM, Jianguo Wu Wrote: >> On 2012/11/26 23:48, H. Peter Anvin wrote: >> >>> On 11/26/2012 05:15 AM, Tang Chen wrote: >>>> >>>> Hi Wu, >>>> >>>> That is really a problem. And, before numa memory got initialized, >>>> memblock subsystem would be used to allocate memory. I didn't find any >>>> approach that could fully address it when I making the patches. There >>>> always be risk that memblock allocates memory on ZONE_MOVABLE. I think >>>> we can only do our best to prevent it from happening. >>>> >>>> Your patch is very helpful. And after a shot look at the code, it seems >>>> that acpi_numa_memory_affinity_init() is an architecture dependent >>>> function. Could we do this somewhere which is not depending on the >>>> architecture ? >>>> >>> >>> The movable memory should be classified as a non-RAM type in memblock, >>> that way we will not allocate from it early on. >>> >>> -hpa >> >> >> yep, we can put movable memory in reserved.regions in memblock. > > Hmm, I don't think so. If so, memory in reserved.regions contain two type > memory: bootmem and movable memory. We will put all pages not in reserved.regions > into buddy system. If we put movable memory in reserved.regions, we have > no chance to put them to buddy system, and can't use them after system boots. > yes, you are right. Or we can fix movablecore_map when add memory region to memblock. > Thanks > Wen Congyang > >> >>> >>> >>> . >>> >> >> >> >> > > > . > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/