linux-kernel - Re: [PATCH v2 5/5] page_alloc: Bootmem limit with movablecore

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 07 Dec 2012 01:28:38 +0800
From:	Jiang Liu <liuj97@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	Wen Congyang <wency@...fujitsu.com>,
	Tang Chen <tangchen@...fujitsu.com>,
	wujianguo <wujianguo106@...il.com>, akpm@...ux-foundation.org,
	rob@...dley.net, isimatu.yasuaki@...fujitsu.com,
	laijs@...fujitsu.com, linfeng@...fujitsu.com, jiang.liu@...wei.com,
	yinghai@...nel.org, kosaki.motohiro@...fujitsu.com,
	minchan.kim@...il.com, mgorman@...e.de, rientjes@...gle.com,
	rusty@...tcorp.com.au, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, linux-doc@...r.kernel.org,
	wujianguo@...wei.com, qiuxishi@...wei.com
Subject: Re: [PATCH v2 5/5] page_alloc: Bootmem limit with movablecore_map

Hi hpa and Tang,
	How do you think about the attached patches, which reserves memory
for hotplug from memblock/bootmem allocator at early booting stages?
	Logically we split the task into three parts:
1) Provide a mechanism to specify zone_movable[] by kernel parameter.
   Patch 1-4 from Tang achieves this goal by adding "movablecore_map" kernel
   parameter.
2) Reserve memory for hotplug by reusing information provided by "movablecore_map".
   Patch 5 from Tang achieve this goal. And the attached patches provides
   another way to achieve the same goal by calling memblock_reserve() and newly
   introduced memblock interfaces.
3) Automatically reserve memory for hotplug according to firmware provided
   information based on the attached patches.

Regards!
Gerry

On 11/27/2012 01:31 PM, H. Peter Anvin wrote:
> On 11/26/2012 07:15 PM, Wen Congyang wrote:
>>
>> Hi, hpa
>>
>> The problem is that:
>> node1 address rang: [18G, 34G), and the user specifies movable map is [8G, 24G).
>> We don't know node1's address range before numa init. So we can't prevent
>> allocating boot memory in the range [24G, 34G).
>>
>> The movable memory should be classified as a non-RAM type in memblock. What
>> do you want to say? We don't save type in memblock because we only
>> add E820_RAM and E820_RESERVED_KERN to memblock.
>>
> 
> We either need to keep the type or not add it to the memblocks.
> 
>     -hpa
> 

--
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/