From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Tang Chen <tangchen@cn.fujitsu.com>,
"jiang.liu@huawei.com" <jiang.liu@huawei.com>,
"wujianguo@huawei.com" <wujianguo@huawei.com>,
"wency@cn.fujitsu.com" <wency@cn.fujitsu.com>,
"laijs@cn.fujitsu.com" <laijs@cn.fujitsu.com>,
"linfeng@cn.fujitsu.com" <linfeng@cn.fujitsu.com>,
"yinghai@kernel.org" <yinghai@kernel.org>,
"rob@landley.net" <rob@landley.net>,
"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>,
"minchan.kim@gmail.com" <minchan.kim@gmail.com>,
"mgorman@suse.de" <mgorman@suse.de>,
"rientjes@google.com" <rientjes@google.com>,
"guz.fnst@cn.fujitsu.com" <guz.fnst@cn.fujitsu.com>,
"rusty@rustcorp.com.au" <rusty@rustcorp.com.au>,
"lliubbo@gmail.com" <lliubbo@gmail.com>,
"jaegeuk.hanse@gmail.com" <jaegeuk.hanse@gmail.com>,
"glommer@parallels.com" <glommer@parallels.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH v5 0/5] Add movablecore_map boot option
Date: Tue, 15 Jan 2013 10:23:20 +0900 [thread overview]
Message-ID: <50F4AF88.9090201@jp.fujitsu.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F1C97C2DA@ORSMSX108.amr.corp.intel.com>
2013/01/15 7:41, Luck, Tony wrote:
>> hm, why. Obviously SRAT support will improve things, but is it
>> actually unusable/unuseful with the command line configuration?
>
> Users will want to set these moveable zones along node boundaries
> (the whole purpose is to be able to remove a node by making sure
> the kernel won't allocate anything tricky in it, right?)
Yes
> So raw addresses
> are usable ... but to get them right the user will have to go parse the
> SRAT table manually to come up with the addresses.
I don't think so because user can easily get raw address by kernel
message in x86.
Here are kernel messages of x86 architecture.
---
[ 0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
[ 0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x7ffffffff]
[ 0.000000] SRAT: Node 1 PXM 2 [mem 0x1000000000-0x17ffffffff]
[ 0.000000] SRAT: Node 2 PXM 3 [mem 0x1800000000-0x1fffffffff]
[ 0.000000] SRAT: Node 3 PXM 4 [mem 0x2000000000-0x27ffffffff]
[ 0.000000] SRAT: Node 4 PXM 5 [mem 0x2800000000-0x2fffffffff]
[ 0.000000] SRAT: Node 5 PXM 6 [mem 0x3000000000-0x37ffffffff]
[ 0.000000] SRAT: Node 6 PXM 7 [mem 0x3800000000-0x3fffffffff]
[ 0.000000] SRAT: Node 7 PXM 1 [mem 0x800000000-0xfffffffff]
---
Thanks,
Yasuaki Ishimatsu
> Any time you
> make the user go off and do some tedious calculation that the computer
> should have done for them is user-abuse.
>
> -Tony
>
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Tang Chen <tangchen@cn.fujitsu.com>,
"jiang.liu@huawei.com" <jiang.liu@huawei.com>,
"wujianguo@huawei.com" <wujianguo@huawei.com>,
"wency@cn.fujitsu.com" <wency@cn.fujitsu.com>,
"laijs@cn.fujitsu.com" <laijs@cn.fujitsu.com>,
"linfeng@cn.fujitsu.com" <linfeng@cn.fujitsu.com>,
"yinghai@kernel.org" <yinghai@kernel.org>,
"rob@landley.net" <rob@landley.net>,
"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>,
"minchan.kim@gmail.com" <minchan.kim@gmail.com>,
"mgorman@suse.de" <mgorman@suse.de>,
"rientjes@google.com" <rientjes@google.com>,
"guz.fnst@cn.fujitsu.com" <guz.fnst@cn.fujitsu.com>,
"rusty@rustcorp.com.au" <rusty@rustcorp.com.au>,
"lliubbo@gmail.com" <lliubbo@gmail.com>,
"jaegeuk.hanse@gmail.com" <jaegeuk.hanse@gmail.com>,
"glommer@parallels.com" <glommer@parallels.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH v5 0/5] Add movablecore_map boot option
Date: Tue, 15 Jan 2013 10:23:20 +0900 [thread overview]
Message-ID: <50F4AF88.9090201@jp.fujitsu.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F1C97C2DA@ORSMSX108.amr.corp.intel.com>
2013/01/15 7:41, Luck, Tony wrote:
>> hm, why. Obviously SRAT support will improve things, but is it
>> actually unusable/unuseful with the command line configuration?
>
> Users will want to set these moveable zones along node boundaries
> (the whole purpose is to be able to remove a node by making sure
> the kernel won't allocate anything tricky in it, right?)
Yes
> So raw addresses
> are usable ... but to get them right the user will have to go parse the
> SRAT table manually to come up with the addresses.
I don't think so because user can easily get raw address by kernel
message in x86.
Here are kernel messages of x86 architecture.
---
[ 0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
[ 0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x7ffffffff]
[ 0.000000] SRAT: Node 1 PXM 2 [mem 0x1000000000-0x17ffffffff]
[ 0.000000] SRAT: Node 2 PXM 3 [mem 0x1800000000-0x1fffffffff]
[ 0.000000] SRAT: Node 3 PXM 4 [mem 0x2000000000-0x27ffffffff]
[ 0.000000] SRAT: Node 4 PXM 5 [mem 0x2800000000-0x2fffffffff]
[ 0.000000] SRAT: Node 5 PXM 6 [mem 0x3000000000-0x37ffffffff]
[ 0.000000] SRAT: Node 6 PXM 7 [mem 0x3800000000-0x3fffffffff]
[ 0.000000] SRAT: Node 7 PXM 1 [mem 0x800000000-0xfffffffff]
---
Thanks,
Yasuaki Ishimatsu
> Any time you
> make the user go off and do some tedious calculation that the computer
> should have done for them is user-abuse.
>
> -Tony
>
next prev parent reply other threads:[~2013-01-15 1:23 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 9:15 [PATCH v5 0/5] Add movablecore_map boot option Tang Chen
2013-01-14 9:15 ` Tang Chen
2013-01-14 9:15 ` [PATCH v5 1/5] x86: get pg_data_t's memory from other node Tang Chen
2013-01-14 9:15 ` Tang Chen
2013-01-14 9:15 ` [PATCH v5 2/5] page_alloc: add movable_memmap kernel parameter Tang Chen
2013-01-14 9:15 ` Tang Chen
2013-01-14 22:35 ` Andrew Morton
2013-01-14 22:35 ` Andrew Morton
2013-01-14 9:15 ` [PATCH v5 3/5] page_alloc: Introduce zone_movable_limit[] to keep movable limit for nodes Tang Chen
2013-01-14 9:15 ` Tang Chen
2013-01-14 9:15 ` [PATCH v5 4/5] page_alloc: Make movablecore_map has higher priority Tang Chen
2013-01-14 9:15 ` Tang Chen
2013-01-14 9:15 ` [PATCH v5 5/5] page_alloc: Bootmem limit with movablecore_map Tang Chen
2013-01-14 9:15 ` Tang Chen
2013-01-14 17:31 ` [PATCH v5 0/5] Add movablecore_map boot option H. Peter Anvin
2013-01-14 17:31 ` H. Peter Anvin
2013-01-14 22:34 ` Andrew Morton
2013-01-14 22:34 ` Andrew Morton
2013-01-14 22:41 ` Luck, Tony
2013-01-14 22:41 ` Luck, Tony
2013-01-14 22:46 ` Andrew Morton
2013-01-16 6:25 ` Yasuaki Ishimatsu
2013-01-16 6:25 ` Yasuaki Ishimatsu
2013-01-16 21:29 ` Andrew Morton
2013-01-16 21:29 ` Andrew Morton
2013-01-16 22:01 ` KOSAKI Motohiro
2013-01-16 22:01 ` KOSAKI Motohiro
2013-01-16 23:00 ` H. Peter Anvin
2013-01-16 23:00 ` H. Peter Anvin
2013-01-17 20:27 ` KOSAKI Motohiro
2013-01-17 20:27 ` KOSAKI Motohiro
2013-01-16 22:52 ` H. Peter Anvin
2013-01-16 22:52 ` H. Peter Anvin
2013-01-17 1:49 ` Tang Chen
2013-01-17 1:49 ` Tang Chen
2013-01-17 20:20 ` KOSAKI Motohiro
2013-01-17 20:20 ` KOSAKI Motohiro
2013-01-17 5:08 ` Yasuaki Ishimatsu
2013-01-17 5:08 ` Yasuaki Ishimatsu
2013-01-17 6:03 ` H. Peter Anvin
2013-01-17 6:03 ` H. Peter Anvin
2013-01-17 16:30 ` Luck, Tony
2013-01-17 16:30 ` Luck, Tony
2013-01-17 20:28 ` KOSAKI Motohiro
2013-01-17 20:28 ` KOSAKI Motohiro
2013-01-18 6:05 ` Yasuaki Ishimatsu
2013-01-18 6:05 ` Yasuaki Ishimatsu
2013-01-18 6:25 ` H. Peter Anvin
2013-01-18 6:25 ` H. Peter Anvin
2013-01-18 7:38 ` Yasuaki Ishimatsu
2013-01-18 7:38 ` Yasuaki Ishimatsu
2013-01-18 8:08 ` Tang Chen
2013-01-18 8:08 ` Tang Chen
2013-01-18 9:23 ` li guang
2013-01-18 9:23 ` li guang
2013-01-18 18:29 ` Luck, Tony
2013-01-18 18:29 ` Luck, Tony
2013-01-19 1:06 ` Jiang Liu
2013-01-19 7:52 ` Chen Gong
2013-01-21 7:36 ` Yasuaki Ishimatsu
2013-01-15 1:23 ` Yasuaki Ishimatsu [this message]
2013-01-15 1:23 ` Yasuaki Ishimatsu
2013-01-15 3:44 ` H. Peter Anvin
2013-01-15 3:44 ` H. Peter Anvin
2013-01-15 4:04 ` Luck, Tony
2013-01-15 4:04 ` Luck, Tony
2013-01-15 0:05 ` Toshi Kani
2013-01-15 0:05 ` Toshi Kani
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=50F4AF88.9090201@jp.fujitsu.com \
--to=isimatu.yasuaki@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=glommer@parallels.com \
--cc=guz.fnst@cn.fujitsu.com \
--cc=hpa@zytor.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-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.