From: Changsheng Liu <liuchangsheng@inspur.com>
To: Vlastimil Babka <vbabka@suse.cz>,
Yasuaki Ishimatsu <yasu.isimatu@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: isimatu.yasuaki@jp.fujitsu.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, yanxiaofeng@inspur.com,
Changsheng Liu <liuchangcheng@inspur.com>
Subject: Re: [PATCH] Memory hot added,The memory can not been added to movable zone
Date: Wed, 26 Aug 2015 15:53:03 +0800 [thread overview]
Message-ID: <55DD705F.7000308@inspur.com> (raw)
In-Reply-To: <55DD58D8.1090508@suse.cz>
a?? 2015/8/26 14:12, Vlastimil Babka a??e??:
> On 26.8.2015 2:36, Changsheng Liu wrote:
>>
>> a?? 2015/8/25 19:13, Vlastimil Babka a??e??:
>>> On 08/25/2015 12:25 PM, Changsheng Liu wrote:
>>>> Thanks very much for your review, I can move the memory from normal zone
>>>> to movable zone succesfully.
>>>> And thank you for let me understand the memory mechanism better.
>>>> a?? 2015/8/25 3:15, Yasuaki Ishimatsu a??e??:
>>> So you agree to drop the patch from -mm?
>> The system add memory to normal zone defaultly so that it can be
>> used by kernel and then we can not move the memory to movable zone.
>> The patch can add the memory to movable zone directlly.
> I thought that you confirmed that the following works?
> echo online_movable > /sys/devices/system/memory/memoryXXX/state
>
> If you want it to be the default, there's the node_movable kernel boot option.
> Does it work for you?
> .
It does not work when memory is hot added.
>
--
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: Changsheng Liu <liuchangsheng@inspur.com>
To: Vlastimil Babka <vbabka@suse.cz>,
Yasuaki Ishimatsu <yasu.isimatu@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: <isimatu.yasuaki@jp.fujitsu.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <yanxiaofeng@inspur.com>,
Changsheng Liu <liuchangcheng@inspur.com>
Subject: Re: [PATCH] Memory hot added,The memory can not been added to movable zone
Date: Wed, 26 Aug 2015 15:53:03 +0800 [thread overview]
Message-ID: <55DD705F.7000308@inspur.com> (raw)
In-Reply-To: <55DD58D8.1090508@suse.cz>
在 2015/8/26 14:12, Vlastimil Babka 写道:
> On 26.8.2015 2:36, Changsheng Liu wrote:
>>
>> 在 2015/8/25 19:13, Vlastimil Babka 写道:
>>> On 08/25/2015 12:25 PM, Changsheng Liu wrote:
>>>> Thanks very much for your review, I can move the memory from normal zone
>>>> to movable zone succesfully.
>>>> And thank you for let me understand the memory mechanism better.
>>>> 在 2015/8/25 3:15, Yasuaki Ishimatsu 写道:
>>> So you agree to drop the patch from -mm?
>> The system add memory to normal zone defaultly so that it can be
>> used by kernel and then we can not move the memory to movable zone.
>> The patch can add the memory to movable zone directlly.
> I thought that you confirmed that the following works?
> echo online_movable > /sys/devices/system/memory/memoryXXX/state
>
> If you want it to be the default, there's the node_movable kernel boot option.
> Does it work for you?
> .
It does not work when memory is hot added.
>
next prev parent reply other threads:[~2015-08-26 7:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 8:18 [PATCH] Memory hot added,The memory can not been added to movable zone Changsheng Liu
2015-08-19 8:18 ` Changsheng Liu
2015-08-19 23:50 ` Andrew Morton
2015-08-19 23:50 ` Andrew Morton
2015-08-20 5:59 ` Changsheng Liu
2015-08-20 5:59 ` Changsheng Liu
2015-08-20 6:12 ` Changsheng Liu
2015-08-20 6:15 ` Changsheng Liu
2015-08-24 19:15 ` Yasuaki Ishimatsu
2015-08-24 19:15 ` Yasuaki Ishimatsu
2015-08-25 10:25 ` Changsheng Liu
2015-08-25 10:25 ` Changsheng Liu
2015-08-25 11:13 ` Vlastimil Babka
2015-08-25 11:13 ` Vlastimil Babka
2015-08-25 11:49 ` Changsheng Liu
2015-08-26 0:36 ` Changsheng Liu
2015-08-26 0:36 ` Changsheng Liu
2015-08-26 6:12 ` Vlastimil Babka
2015-08-26 6:12 ` Vlastimil Babka
2015-08-26 7:53 ` Changsheng Liu [this message]
2015-08-26 7:53 ` Changsheng Liu
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=55DD705F.7000308@inspur.com \
--to=liuchangsheng@inspur.com \
--cc=akpm@linux-foundation.org \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuchangcheng@inspur.com \
--cc=vbabka@suse.cz \
--cc=yanxiaofeng@inspur.com \
--cc=yasu.isimatu@gmail.com \
/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.