linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Simon Jeons <simon.jeons@gmail.com>
To: Tang Chen <tangchen@cn.fujitsu.com>
Cc: Jiang Liu <jiang.liu@huawei.com>,
	Jianguo Wu <wujianguo@huawei.com>,
	hpa@zytor.com, akpm@linux-foundation.org, wency@cn.fujitsu.com,
	laijs@cn.fujitsu.com, linfeng@cn.fujitsu.com, yinghai@kernel.org,
	isimatu.yasuaki@jp.fujitsu.com, rob@landley.net,
	kosaki.motohiro@jp.fujitsu.com, minchan.kim@gmail.com,
	mgorman@suse.de, rientjes@google.com, rusty@rustcorp.com.au,
	lliubbo@gmail.com, jaegeuk.hanse@gmail.com, tony.luck@intel.com,
	glommer@parallels.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 3/5] page_alloc: Introduce zone_movable_limit[] to keep movable limit for nodes
Date: Wed, 12 Dec 2012 21:09:31 -0600	[thread overview]
Message-ID: <1355368171.1436.1.camel@kernel.cn.ibm.com> (raw)
In-Reply-To: <50C933E2.3070608@cn.fujitsu.com>

On Thu, 2012-12-13 at 09:48 +0800, Tang Chen wrote:
> 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. :)
> 

[    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 c0c2cc00, node_mem_map
f19c2200
[    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


menuentry 'Fedora (3.7.0+)' --class fedora --class gnu-linux --class gnu
--class os $menuentry_id_option
'gnulinux-simple-7ed9528d-006f-4d9e-93d9-f68b0967ca99' {
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_msdos
        insmod ext2
        set root='hd0,msdos1'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1'
eba9dfce-d7f1-4b5c-9199-f2abf80e5dc6
        else
          search --no-floppy --fs-uuid --set=root
eba9dfce-d7f1-4b5c-9199-f2abf80e5dc6
        fi
        echo 'Loading Fedora (3.7.0+)'
        linux   /vmlinuz-3.7.0+ root=/dev/mapper/vg_kernel-lv_root ro
rd.md=0 rd.dm=0 rd.lvm.lv=vg_kernel/lv_root SYSFONT=True  KEYTABLE=us
rd.luks=0 LANG=en_US.UTF-8 rd.lvm.lv=vg_kernel/lv_swap rhgb quiet
        echo 'Loading initial ramdisk ...'
        initrd /initramfs-3.7.0+.img
}


> 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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2012-12-13  3:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11  2:33 [PATCH v3 0/5] Add movablecore_map boot option Tang Chen
2012-12-11  2:33 ` [PATCH v3 1/5] x86: get pg_data_t's memory from other node Tang Chen
2012-12-11  2:33 ` [PATCH v3 2/5] page_alloc: add movable_memmap kernel parameter Tang Chen
2012-12-11  2:33 ` [PATCH v3 3/5] page_alloc: Introduce zone_movable_limit[] to keep movable limit for nodes Tang Chen
2012-12-11  3:07   ` Jianguo Wu
2012-12-11  3:32     ` Tang Chen
2012-12-11 11:28       ` Simon Jeons
2012-12-12  0:49         ` Jiang Liu
2012-12-12  9:09           ` Tang Chen
2012-12-12  9:29             ` Simon Jeons
2012-12-12 10:32               ` Tang Chen
2012-12-13  0:28                 ` Simon Jeons
2012-12-13  1:48                   ` Tang Chen
2012-12-13  3:09                     ` Simon Jeons [this message]
2012-12-11 12:24     ` Simon Jeons
2012-12-11 12:41       ` Jianguo Wu
2012-12-11 13:20         ` Simon Jeons
2012-12-12  1:57           ` Jianguo Wu
2012-12-12  2:03             ` Simon Jeons
2012-12-12  1:58           ` Lin Feng
2012-12-11  4:55   ` [PATCH v3 3/5][RESEND] " Tang Chen
2012-12-11  2:33 ` [PATCH v3 4/5] page_alloc: Make movablecore_map has higher priority Tang Chen
2012-12-11  4:56   ` [PATCH v3 4/5][RESEND] " Tang Chen
2012-12-12  1:33     ` Simon Jeons
2012-12-12  9:34       ` Tang Chen
2012-12-13  1:56         ` Simon Jeons
2012-12-11  2:33 ` [PATCH v3 5/5] page_alloc: Bootmem limit with movablecore_map Tang Chen
2012-12-11 11:33 ` [PATCH v3 0/5] Add movablecore_map boot option Simon Jeons

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=1355368171.1436.1.camel@kernel.cn.ibm.com \
    --to=simon.jeons@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=glommer@parallels.com \
    --cc=hpa@zytor.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=jaegeuk.hanse@gmail.com \
    --cc=jiang.liu@huawei.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linfeng@cn.fujitsu.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lliubbo@gmail.com \
    --cc=mgorman@suse.de \
    --cc=minchan.kim@gmail.com \
    --cc=rientjes@google.com \
    --cc=rob@landley.net \
    --cc=rusty@rustcorp.com.au \
    --cc=tangchen@cn.fujitsu.com \
    --cc=tony.luck@intel.com \
    --cc=wency@cn.fujitsu.com \
    --cc=wujianguo@huawei.com \
    --cc=yinghai@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).