All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tang Chen <tangchen@cn.fujitsu.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
	"Luck, Tony" <tony.luck@intel.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: Thu, 17 Jan 2013 09:49:48 +0800	[thread overview]
Message-ID: <50F758BC.5070308@cn.fujitsu.com> (raw)
In-Reply-To: <50F72F17.9030805@zytor.com>

On 01/17/2013 06:52 AM, H. Peter Anvin wrote:
> On 01/16/2013 01:29 PM, Andrew Morton wrote:
>>>
>>> Yes. If SRAT support is available, all memory which enabled hotpluggable
>>> bit are managed by ZONEMOVABLE. But performance degradation may
>>> occur by NUMA because we can only allocate anonymous page and page-cache
>>> from these memory.
>>>
>>> In this case, if user cannot change SRAT information, user needs a way to
>>> select/set removable memory manually.
>>
>> If I understand this correctly you mean that once SRAT parsing is
>> implemented, the user can use movablecore_map to override that SRAT
>> parsing, yes?  That movablecore_map will take precedence over SRAT?
>>
>
> Yes,

Hi HPA, Andrew,

No, I don't think so. In my [PATCH v4 3/6], I checked if users specified the
unhotpluggable memory ranges, I will remove them from movablecore_map.map[].
So this option will not override SRAT.

It works like this:

    hotpluggable ranges:            |-----------------|
    unhotpluggable ranges:  |-----|                      |--------|
    user specified ranges:   |---|       |--------------------|
    movablecore_map.map[]:               |------------|

Please refer to https://lkml.org/lkml/2012/12/19/53.

But in this v5 patch-set, I remove all SRAT related code. So this v5 users'
option will override SRAT.


Thanks. :)

>but we still need a higher-level user interface which specifies
> which nodes, not which memory ranges, should be movable.  That is the
> policy granularity that is actually appropriate for the administrator
> (trading off performance vs reliability.)
>
> 	-hpa
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

--
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: Tang Chen <tangchen@cn.fujitsu.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
	"Luck, Tony" <tony.luck@intel.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: Thu, 17 Jan 2013 09:49:48 +0800	[thread overview]
Message-ID: <50F758BC.5070308@cn.fujitsu.com> (raw)
In-Reply-To: <50F72F17.9030805@zytor.com>

On 01/17/2013 06:52 AM, H. Peter Anvin wrote:
> On 01/16/2013 01:29 PM, Andrew Morton wrote:
>>>
>>> Yes. If SRAT support is available, all memory which enabled hotpluggable
>>> bit are managed by ZONEMOVABLE. But performance degradation may
>>> occur by NUMA because we can only allocate anonymous page and page-cache
>>> from these memory.
>>>
>>> In this case, if user cannot change SRAT information, user needs a way to
>>> select/set removable memory manually.
>>
>> If I understand this correctly you mean that once SRAT parsing is
>> implemented, the user can use movablecore_map to override that SRAT
>> parsing, yes?  That movablecore_map will take precedence over SRAT?
>>
>
> Yes,

Hi HPA, Andrew,

No, I don't think so. In my [PATCH v4 3/6], I checked if users specified the
unhotpluggable memory ranges, I will remove them from movablecore_map.map[].
So this option will not override SRAT.

It works like this:

    hotpluggable ranges:            |-----------------|
    unhotpluggable ranges:  |-----|                      |--------|
    user specified ranges:   |---|       |--------------------|
    movablecore_map.map[]:               |------------|

Please refer to https://lkml.org/lkml/2012/12/19/53.

But in this v5 patch-set, I remove all SRAT related code. So this v5 users'
option will override SRAT.


Thanks. :)

>but we still need a higher-level user interface which specifies
> which nodes, not which memory ranges, should be movable.  That is the
> policy granularity that is actually appropriate for the administrator
> (trading off performance vs reliability.)
>
> 	-hpa
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

  reply	other threads:[~2013-01-17  1:50 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 [this message]
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
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=50F758BC.5070308@cn.fujitsu.com \
    --to=tangchen@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=glommer@parallels.com \
    --cc=guz.fnst@cn.fujitsu.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-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=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.