All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"Luck, Tony" <tony.luck@intel.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: Wed, 16 Jan 2013 22:03:14 -0800	[thread overview]
Message-ID: <50F79422.6090405@zytor.com> (raw)
In-Reply-To: <50F78750.8070403@jp.fujitsu.com>

On 01/16/2013 09:08 PM, Yasuaki Ishimatsu wrote:
>
> I thought about the method of specifying the node. But I think
> this method is inconvenience. Node number is decided by OS.
> So the number is changed easily.
>
> for example:
>
> o exmaple 1
>    System has 3 nodes:
>    node0, node1, node2
>
>    When user remove node1, the system has:
>    node0, node2
>
>    But after rebooting the system, the system has:
>    node0, node1
>
>    So node2 becomes node1.
>
> o example 2:
>    System has 2 nodes:
>    0x40000000 - 0x7fffffff : node0
>    0xc0000000 - 0xffffffff : node1
>
>    When user add a node wchih memory range is [0x80000000 - 0xbfffffff],
>    system has:
>    0x40000000 - 0x7fffffff : node0
>    0xc0000000 - 0xffffffff : node1
>    0x80000000 - 0xbfffffff : node2
>
>    But after rebooting the system, the system's node may become:
>    0x40000000 - 0x7fffffff : node0
>    0x80000000 - 0xbfffffff : node1
>    0xc0000000 - 0xffffffff : node2
>
>    So node nunber is changed.
>
> Specifying node number may be easy method than specifying memory
> range. But if user uses node number for specifying removable memory,
> user always need to care whether node number is changed or not at
> every hotplug operation.
>


Well, there are only two options:

1. The user doesn't care which nodes are movable.  In that case, the 
user may just want to specify a target as a percentage of memory to make 
movable -- effectively a "slider" on the performance vs. reliability 
spectrum.  The kernel can then assign nodes arbitrarily.

2. If the user *does* care which nodes are movable, then the user needs 
to be able to specify that *in a way that makes sense to the user*. 
This may mean involving the DMI information as well as SRAT in order to 
get "silk screen" type information out.

	-hpa



-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
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: "H. Peter Anvin" <hpa@zytor.com>
To: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"Luck, Tony" <tony.luck@intel.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: Wed, 16 Jan 2013 22:03:14 -0800	[thread overview]
Message-ID: <50F79422.6090405@zytor.com> (raw)
In-Reply-To: <50F78750.8070403@jp.fujitsu.com>

On 01/16/2013 09:08 PM, Yasuaki Ishimatsu wrote:
>
> I thought about the method of specifying the node. But I think
> this method is inconvenience. Node number is decided by OS.
> So the number is changed easily.
>
> for example:
>
> o exmaple 1
>    System has 3 nodes:
>    node0, node1, node2
>
>    When user remove node1, the system has:
>    node0, node2
>
>    But after rebooting the system, the system has:
>    node0, node1
>
>    So node2 becomes node1.
>
> o example 2:
>    System has 2 nodes:
>    0x40000000 - 0x7fffffff : node0
>    0xc0000000 - 0xffffffff : node1
>
>    When user add a node wchih memory range is [0x80000000 - 0xbfffffff],
>    system has:
>    0x40000000 - 0x7fffffff : node0
>    0xc0000000 - 0xffffffff : node1
>    0x80000000 - 0xbfffffff : node2
>
>    But after rebooting the system, the system's node may become:
>    0x40000000 - 0x7fffffff : node0
>    0x80000000 - 0xbfffffff : node1
>    0xc0000000 - 0xffffffff : node2
>
>    So node nunber is changed.
>
> Specifying node number may be easy method than specifying memory
> range. But if user uses node number for specifying removable memory,
> user always need to care whether node number is changed or not at
> every hotplug operation.
>


Well, there are only two options:

1. The user doesn't care which nodes are movable.  In that case, the 
user may just want to specify a target as a percentage of memory to make 
movable -- effectively a "slider" on the performance vs. reliability 
spectrum.  The kernel can then assign nodes arbitrarily.

2. If the user *does* care which nodes are movable, then the user needs 
to be able to specify that *in a way that makes sense to the user*. 
This may mean involving the DMI information as well as SRAT in order to 
get "silk screen" type information out.

	-hpa



-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2013-01-17  6:03 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 [this message]
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
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=50F79422.6090405@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@linux-foundation.org \
    --cc=glommer@parallels.com \
    --cc=guz.fnst@cn.fujitsu.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-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.