在 2015/11/5 0:31, Dave Hansen 写道:
On 11/04/2015 12:23 AM, liuchangsheng wrote:
After the user config CONFIG_MOVABLE_NODE,
When the memory is hot added, should_add_memory_movable() return 0
because all zones including ZONE_MOVABLE are empty,
so the memory that was hot added will be assigned to
patch. Please see below.
Thanks，I will update the patch and repost it
On Tue, 15 Sep 2015 03:49:58 -0400
Changsheng Liu wrote:
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE and movable_node kernel option,
When the memory is hot added, should_add_memory_movable() return 0
在 2015/10/15 0:18, Vlastimil Babka 写道:
On 10/12/2015 08:58 AM, Changsheng Liu wrote:
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE,
When the memory is hot added, should_add_memory_movable() return 0
because all zones including ZONE_MOVABLE are empty,
so the memory that was
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE,
When the memory is hot added, should_add_memory_movable() return 0
because all zones including ZONE_MOVABLE are empty,
so the memory that was hot added will be assigned to ZONE_NORMAL
and ZONE_NORMAL will be created firstly.
But we
t is useful. :)
And BTW, please don't cc the following reviewers. Their email addresses
have changed.
Cc: Zhang Yanfei
Cc: Hu Tao
Cc: Lai Jiangshan
Cc: Gu Zheng
Thanks. :)
On 10/09/2015 03:12 PM, Changsheng Liu wrote:
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE,
When t
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE,
When the memory is hot added, should_add_memory_movable() return 0
because all zones including movable zone are empty,
so the memory that was hot added will be added to the normal zone
and the normal zone will be created firstly
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE and movable_node kernel option,
When the memory is hot added, should_add_memory_movable() return 0
because all zones including movable zone are empty,
so the memory that was hot added will be added to the normal zone
and the normal
On 9/1/2015 23:37, Yasuaki Ishimatsu wrote:
On Mon, 31 Aug 2015 01:58:40 -0400
Changsheng Liu wrote:
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE and movable_node kernel option,
When the memory is hot added, should_add_memory_movable() return 0
because all zones
On 9/1/2015 23:37, Yasuaki Ishimatsu wrote:
On Mon, 31 Aug 2015 01:58:40 -0400
Changsheng Liu wrote:
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE and movable_node kernel option,
When the memory is hot added, should_add_memory_movable() return 0
because all zones
On 8/31/2015 21:08, Vlastimil Babka wrote:
On 08/31/2015 07:58 AM, Changsheng Liu wrote:
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE and movable_node kernel
option,
When the memory is hot added, should_add_memory_movable() return 0
because all zones including movable
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE and movable_node kernel option,
When the memory is hot added, should_add_memory_movable() return 0
because all zones including movable zone are empty,
so the memory that was hot added will be added to the normal zone
and the normal
在 2015/8/27 17:29, Vlastimil Babka 写道:
On 08/27/2015 10:54 AM, Changsheng Liu wrote:
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE and movable_node kernel
option,
When the memory is hot added, should_add_memory_movable() return 0
because all zones including movable zone
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE and movable_node kernel option,
When the memory is hot added, should_add_memory_movable() return 0
because all zones including movable zone are empty,
so the memory that was hot added will be added to the normal zone
and the normal
在 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
First, thanks very much for your review, I will update codes according
to your suggestion
On 2015/8/25 21:12, Yasuaki Ishimatsu wrote:
On Thu, 20 Aug 2015 03:28:05 -0400
Changsheng Liu wrote:
From: Changsheng Liu
When memory is hot added, should_add_memory_movable() always returns 0
在 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 写道
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 写道:
Hi
On Thu, 20 Aug 2015 14:15:13 +0800
Changsheng Liu wrote:
Hi Andrew Morton:
First
On 08/20/201515:41, Vlastimil Babka wrote:
On 08/20/2015 09:28 AM, Changsheng Liu wrote:
From: Changsheng Liu
When memory is hot added, should_add_memory_movable() always returns 0
because the movable zone is empty, so the memory that was hot added will
add to the normal zone even if we want
From: Changsheng Liu
When memory is hot added, should_add_memory_movable() always returns 0
because the movable zone is empty, so the memory that was hot added will
add to the normal zone even if we want to remove the memory.
So we change should_add_memory_movable(): if the user config
hot added we let the memory be added to movable
zone,
so we will be able to hot remove the memory that have been hot added
On Wed, 20 Aug 2015 7:50, Andrew Morton wrote:
On Wed, 19 Aug 2015 04:18:26 -0400 Changsheng Liu
wrote:
From: Changsheng Liu
When memory hot added, th
From: Changsheng Liu
When memory hot added, the function should_add_memory_movable
always return 0,because the movable zone is empty,
so the memory that hot added will add to normal zone even if
we want to remove the memory.
So we change the function should_add_memory_movable,if the user
config
From: Changsheng Liu
---
mm/memory_hotplug.c |9 +++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 26fbba7..f5bcd03 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -1198,8 +1198,13 @@ static int
22 matches
Mail list logo
