linux-kernel - Re: [PATCH v3 3/5] page_alloc: Introduce zone_movable

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]

Message-ID: <50C933E2.3070608@cn.fujitsu.com>
Date:	Thu, 13 Dec 2012 09:48:18 +0800
From:	Tang Chen <tangchen@...fujitsu.com>
To:	Simon Jeons <simon.jeons@...il.com>
CC:	Jiang Liu <jiang.liu@...wei.com>,
	Jianguo Wu <wujianguo@...wei.com>, hpa@...or.com,
	akpm@...ux-foundation.org, wency@...fujitsu.com,
	laijs@...fujitsu.com, linfeng@...fujitsu.com, yinghai@...nel.org,
	isimatu.yasuaki@...fujitsu.com, rob@...dley.net,
	kosaki.motohiro@...fujitsu.com, minchan.kim@...il.com,
	mgorman@...e.de, rientjes@...gle.com, rusty@...tcorp.com.au,
	lliubbo@...il.com, jaegeuk.hanse@...il.com, tony.luck@...el.com,
	glommer@...allels.com, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH v3 3/5] page_alloc: Introduce zone_movable_limit[] to
 keep movable limit for nodes

On 12/13/2012 08:28 AM, Simon Jeons wrote:
> On Wed, 2012-12-12 at 18:32 +0800, Tang Chen wrote:
>> Hi Simon,
>>
>> On 12/12/2012 05:29 PM, Simon Jeons wrote:
>>>
>>> Thanks for your clarify.
>>>
>>> Enable PAE on x86 32bit kernel, 8G memory, movablecore=6.5G
>>
>> Could you please provide more info ?
>>
>> Such as the whole kernel commondline. And did this happen after
>> you applied these patches ? What is the output without these
>> patches ?
>
> This result is without the patches, I didn't add more kernel
> commandline, just movablecore=6.5G, but output as you see is strange, so
> what happened?

Hi Simon,

For now, I'm not quite sure what happened. Could you please provide the
output without the movablecore=6.5G option ?

Seeing from your output, your totalpages=2051391, which is about 8G. But
the memory mapped for your node 0 is obviously not enough.

When we have high memory, ZONE_MOVABLE is taken from ZONE_HIGH. So the
first line, 8304MB HIGHMEM available is also strange.

So I think we need more info to find out the problem. :)

Thank. :)

>
>>
>> Thanks. :)
>>
>>>>
>>>> [    0.000000] 8304MB HIGHMEM available.
>>>> [    0.000000] 885MB LOWMEM available.
>>>> [    0.000000]   mapped low ram: 0 - 375fe000
>>>> [    0.000000]   low ram: 0 - 375fe000
>>>> [    0.000000] Zone ranges:
>>>> [    0.000000]   DMA      [mem 0x00010000-0x00ffffff]
>>>> [    0.000000]   Normal   [mem 0x01000000-0x375fdfff]
>>>> [    0.000000]   HighMem  [mem 0x375fe000-0x3e5fffff]
>>>> [    0.000000] Movable zone start for each node
>>>> [    0.000000] Early memory node ranges
>>>> [    0.000000]   node   0: [mem 0x00010000-0x0009cfff]
>>>> [    0.000000]   node   0: [mem 0x00100000-0x1fffffff]
>>>> [    0.000000]   node   0: [mem 0x20200000-0x3fffffff]
>>>> [    0.000000]   node   0: [mem 0x40200000-0xb69cbfff]
>>>> [    0.000000]   node   0: [mem 0xb6a46000-0xb6a47fff]
>>>> [    0.000000]   node   0: [mem 0xb6b1c000-0xb6cfffff]
>>>> [    0.000000]   node   0: [mem 0x00000000-0x3e5fffff]
>>>> [    0.000000] On node 0 totalpages: 2051391
>>>> [    0.000000] free_area_init_node: node 0, pgdat c0c26a80,
>>>> node_mem_map
>>>> f19de200
>>>> [    0.000000]   DMA zone: 32 pages used for memmap
>>>> [    0.000000]   DMA zone: 0 pages reserved
>>>> [    0.000000]   DMA zone: 3949 pages, LIFO batch:0
>>>> [    0.000000]   Normal zone: 1740 pages used for memmap
>>>> [    0.000000]   Normal zone: 220466 pages, LIFO batch:31
>>>> [    0.000000]   HighMem zone: 16609 pages used for memmap
>>>> [    0.000000]   HighMem zone: 1808595 pages, LIFO batch:31
>>>
>>> Why zone movable disappear?
>>>
>>>
>>>
>>>
>>
>
>
>

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